Caught ban for fork deepNude on gitlab.com

In one of the articles published on Habré, I read in the comments that there are copies of deepNude on gitlab.com , I found it out of curiosity and made a fork “just in case”. 3 hours after this, I could not run the code, since flew to the ban



After correspondence with the support, it turned out that I had violated the rules of their service and that I had been unlocked, but I had to remove deepNude from my acca within 24 hours.

But I couldn’t come in, probably because of the two-factor enabled and incorrect unlocking:
')


While I was waiting for another response from the support, I was overwhelmed with the thought “It’s unreliable to store the code on gitlab.com, the rules may change, and you have all the work tied to them, you cannot even deploy the registry and CI / CD bypassing them”.

But the fact is that the guitarb is convenient, and I really don't understand how you can live in 2019 without their CI / CD. And other goodies. Vobschem raised a separate server rolled there docker / docker-compose / gitlab runner / Gitlab CE / registry did not raise (Amazon Amazon ECR)

Everything, now the deployments do not depend on the policies of the service administration. I am pleased and suddenly a letter comes that this time I was completely unblocked. I deleted deepNude, and transferred all my repositories (and there are more than 50 of them) with one click of the mouse to the selfHosting version of Gitlab.

Eventually

Of the benefits:

1. Build and Deploy doubled! from 6 minutes to 3x (build / test / deploy for the product)
2. There was full control of all kinds of processes through the Gitlab CE admin panel.
3. No dependence on service policies, here you are your own boss
4. Subjectively, Gitlab CE works much faster than the cloud version in all aspects.

Of the minuses:

1. We need to make backups (I do the built-in backup mechanism from DigitalOcean)
2. 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. Probably if it were not for this case - it had not occurred to me to do this.

If anyone is interested, I can post docker-compose configs to run my Gitlab CE and CI / CD configuration examples.

Have a good work week everyone!

UPD: As correctly noted in the comments amarao :

I would not consider in-house backup hosting service reliable. One blast in billing, and there is no instance or backup

Therefore, in addition to backing up to DO, I set up a native backup mechanism in Gitlab CE , now I’m doing a dump of the base and repositories on Amazon S3, from which you can easily recover (but for the experiment, you will need to try the restore, I’ll see what will be released).

You can also use Repository mirroring