@souldessin how much time did it take to install/setup?
@worldsendless
With compose it was really just an hour or so, with certs, port forwarding, etc. It actually took a little longer than normal because I had another server on that ip that had ssh on. I passed gitlab's ssh through another ip that didn't.
@worldsendless we have a GitLab instance on-prem running for the last 4 or 5 years.
We haven't had any major issues, but we don't use it a lot (only as git repo, we have started to use gitlab-ci this year)
Just be prepared to update it every single month, maybe more 😅 (that's the first thing we automated)
@worldsendless we've run it for many years on-prem along with some Windows and some Linux runners for the CI, all as docker-based installs. We've had no significant issues that I can recall. The attention to detail on upgrades is impressive - even upgrading 2 major versions forward from our regretfully-stale install was smooth and trouble free.
@worldsendless
I've been hosting it for my own development and I like that the built-in ci/cd. It's only me, but it's served me well. The ram usage is high, 2.5gb, but not bad.
I also run it via docker compose for easier updating.