July 15, 2019 at 14:50Caught a ban for fork deepNude on gitlab.com
In one of the articles published on the hub, I read in the comments that there are copies of deepNude on gitlab.com , purely out of curiosity I found it and made a fork “just in case”. 3 hours after that, I could not run the code, because flew into the ban ...
After correspondence with support it turned out that I had violated the rules of their service and that they had unlocked me, but I had to remove deepNude from my account within 24 hours.
But I couldn’t enter, probably due to the included two-factor and incorrect unlocking:
While I was waiting for the next response from the support, I wondered “Keeping the code on gitlab.com unreliable, the rules can change, and you have all the work tied to them "You can’t even make a deploy bypassing their registry and CI / CD."
But the fact is that gitlab is convenient, and I really do not understand how you can live in 2019 without their CI / CD. And other goodies. In general, I lifted a separate server, rolled it there docker / docker-compose / gitlab runner / Gitlab CE / registry did not raise it (Amazon ECR)
, now deployments do not depend on service administration policies. I am satisfied and suddenly a letter arrives saying that this time I was completely unblocked. I deleted deepNude, and transferred all my repositories (and there are more than 50) with one click to the selfHosting version of Gitlab.
From the pros:
Of the minuses:
In general, clone deepNude (if it is still there) and have to move to your gitlab)), you will not regret it. Probably if it weren’t for this case, it didn’t occur to me to do this.
If anyone is interested, I can upload docker-compose configs to launch my Gitlab CE and CI / CD configuration examples.
Have a good working week!
UPD: As amarao correctly noted in the comments :
Therefore, in addition to the backup on DO, I configured the native backup mechanism in Gitlab CE , now the dump of the database and repositories on Amazon S3 is done on the crown, from which you can easily recover (but for the experiment you will need to conduct a trial recovery, I'll see what comes of it )
You can also use Repository mirroring
After correspondence with support it turned out that I had violated the rules of their service and that they had unlocked me, but I had to remove deepNude from my account within 24 hours.
But I couldn’t enter, probably due to the included two-factor and incorrect unlocking:
While I was waiting for the next response from the support, I wondered “Keeping the code on gitlab.com unreliable, the rules can change, and you have all the work tied to them "You can’t even make a deploy bypassing their registry and CI / CD."
But the fact is that gitlab is convenient, and I really do not understand how you can live in 2019 without their CI / CD. And other goodies. In general, I lifted a separate server, rolled it there docker / docker-compose / gitlab runner / Gitlab CE / registry did not raise it (Amazon ECR)
, now deployments do not depend on service administration policies. I am satisfied and suddenly a letter arrives saying that this time I was completely unblocked. I deleted deepNude, and transferred all my repositories (and there are more than 50) with one click to the selfHosting version of Gitlab.
Eventually
From the pros:
- Builds and deployments accelerated twice! from 6 minutes to 3x (assembly / testing / deployment for prod)
- There was a complete control of various processes through the admin panel Gitlab CE
- There is no dependence on service policies, here you are your own boss
- Subjectively, Gitlab CE works much faster than the cloud version in all aspects.
Of the minuses:
- It is necessary to make backups (I do the built-in backup mechanism at DigitalOcean)
- It is necessary to periodically update and monitor the status of the server / containers
In general, clone deepNude (if it is still there) and have to move to your gitlab)), you will not regret it. Probably if it weren’t for this case, it didn’t occur to me to do this.
If anyone is interested, I can upload docker-compose configs to launch my Gitlab CE and CI / CD configuration examples.
Have a good working week!
UPD: As amarao correctly noted in the comments :
I would not consider the in-house backup service of the hoster reliable. One explosion in billing, and there is no instance, no backup
Therefore, in addition to the backup on DO, I configured the native backup mechanism in Gitlab CE , now the dump of the database and repositories on Amazon S3 is done on the crown, from which you can easily recover (but for the experiment you will need to conduct a trial recovery, I'll see what comes of it )
You can also use Repository mirroring
