4 ms·
Same here. After a few years and moving it around from server to server (switched hosts a couple times), it's run flawlessly and upgrades are just one apt-get u
by leetbulb 8y ago
Same here. After a few years and moving it around from server to server (switched hosts a couple times), it's run flawlessly and upgrades are just one apt-get upgrade away...never had a single issue with that. We have 40+ projects and utilize container registry and CI with Kubernetes as well.
- naikrovek 8y agoDang. Afaict, you guys are the exceptions to the rule. I guess you folks gave it enough hardware to run properly. From what I'm reading that's what's missing in a lot of failing installations. It seems particularly resource hungry.
- theyinwhy 8y agoCode repository management is a central part of every company. I don't see any problem in throwing sufficient hardware at such a crucial piece of software. Relevant: https://docs.gitlab.com/ee/install/requirements.html#hardware-requirements https://docs.gitlab.com/ee/install/requirements.html#hardwar...
- naikrovek 8y agoThank you. I wonder why the advise a minimum of 4GB of RAM and offer a build for Raspberry Pi. Changing that URL from "/ee/" to "/ce/" gives the same RAM requirements.
- theyinwhy 8y agoI would be guessing someone at gitlab was playing around with his/her Raspberry. But yeah, I would advise against running anything important on a Raspberry ;).
- leetbulb 8y agoIt's currently running as an omnibus installation on a KVM node. 8GB of memory and 4 vCPU (E3-1230v6). Anything more than 4GB of memory and a couple cores appears to be sufficient for our use.
- Lazare 8y agoActually, one of the things we're liking about Gitlab is how lightweight it is. ...of course, it replaced Upsource for us, and Upsource is incredibly resource hungry, so maybe we just have a very, very skewed frame of reference. :)