3 ms·
If you're going to run gitlab, I would suggest using the docker image and docker-compose to run it. Just done this upgrade: two commands, took 30s.
by dflock 5y ago
If you're going to run gitlab, I would suggest using the docker image and docker-compose to run it. Just done this upgrade: two commands, took 30s.
- hobo_mark 5y agoWhat are the system requirements for a personal setup? I mean > 4GB RAM is the required minimum memory size and supports up to 500 users How far down does it scale to just a handful of users though? (usual free vps are about 1GB, and are normally used to run other things as well) EDIT: found it, unfortunately not as much as I would have hoped (but not unexpected) > Minimum 2GB of RAM + 1GB of SWAP > You should be able to run GitLab with up to 5 developers with individual Git projects no larger than 100MB. https://docs.gitlab.com/omnibus/settings/memory_constrained_envs.html https://docs.gitlab.com/omnibus/settings/memory_constrained_...
- hedora 5y agoIt looks like gogs only requires 512MB. It might be a better choice for resource constrained environments. https://github.com/gogs/gogs/issues/5487 https://github.com/gogs/gogs/issues/5487
- deleted 5y ago[deleted]
- ninjaoxygen 5y agoMy only annoyance with GitLab on that front is the lack of tags for "14.8-ce" to enable use of watchtower to keep the minor/security patch up to date, like we have on other images. I definitely do not want to use "latest", in the past there have been updates or intervention required between major versions.
- Netcob 5y agoAm I missing something? In my experience, updating gitlab involves looking at either the docker hub page with the tags or that gitlab news page that I'm trying to find right now and then painfully going from minor to minor. If you update every week you're probably fine, but if you skip a version some database migrations might not work and then the real fun begins.