Thank you Gogs. You will be missed.

I've recently started using GitLab for my source control. It is a PIG on resources compared to Gogs. But, it is also quite feature rich. I kind of wish that I could use a SQLite backend as opposed to PostgresSQL given the relatively small scale of my projects. But, I can't complain. I upgraded my server with more RAM, an NVMe drive and a better processor so I guess I can't complain that I'm making use of it.

But, the best thing about the whole experience was how seamless it was to get my projects out of Gogs and up and running in GitLab. Firstly, I just imported the repositories directly via URL. And then I redirected my Gogs URL to match my GitLab one, tweaked my git config in the hidden folders and... Voila! Everything just worked. 

Then I updated my server scripts to backup my GitLab instance instead of Gogs, removed all of the old files and I'm happy now.

Why? Gogs is great. Don't get me wrong there. If you're JUST interested in version control and nothing else, then I would say it is my #1 recommendation. Especially given how easy it is to migrate to another solution later if you outgrow that original use case as I did.

If you need more and you want self hosted, then GitLab is my recommendation.

Outside of that I would say Azure DevOps for personal projects and GitHub for larger projects.

In the meantime, I'm a little sad to see that I've outgrown Gogs. The footprint it consumes for the value it brings is simply remarkable.

But, I wanted the CI/CD pipeline and I didn't want to bolt something on after the fact. Especially not after having invested time in learning GitLab's solution. I'm at a point now where I can get a reasonable pipeline up and running for a project in a few minutes and maybe a few tries to sort out the little bits I missed when migrating my old build procedures.

So, Gogs had to go.