Eh. The method described in this post (ie bare repositories on a filesystem and ssh transport) is perfectly sufficient for my personal use if I'm hosting. The minute there's a MySQL dependency I'm a hard pass...

I buy the need for the gitlabs of the world when multiple users show up, if only because managing credentials is a pain. But for single user use cases I wouldn't waste my time.

The instructions say that you can just use SQLite, though.

"Based on your choice, install one of supported databases or skip this step"

> I buy the need for the gitlabs of the world when multiple users show up, if only because managing credentials is a pain.

gitolite has worked well for small multiuser teams for me. No difficulty with managing credentials and no need for a heavy solution.

Both gogs and gitea (forked from gogs) support using sqlite instead of mysql. This means there's no external database server to deal with, and since it's a small use set of private repositories it performs quite well.

I moved to https://gitea.io/ myself, largely because it seems to be more frequently updated these days.

definitely the best git repo for small teams! better than gitolite and manual hosting, lighter than gitlab, the best for me.

Do you do code review in your teams? That's the main reason that I am using Gitlab over Gogs/Gitea for my team.

https://github.com/go-gitea/gitea/issues/189 should have it soon