151–160 of 162 posts
Earlier quoted context omitted.
This is just utterly wrong. yum upgrade Done. No problems for years now. Not a single one.
Are you using it? I've yet to come across anyone hosting their own gitlab instance that has not had trouble of some sort.
Earlier quoted context omitted.
We went Gitlab to Bitbucket + Jira. Quite a bit more power, for less money (even after paying for cloud testers).
I’ve been wondering why Bitbucket just gets ignored with all the Github news. I get that Gitlab is the new hotness but they’ve been offering free private repos before gitlab was even a thing.
Earlier quoted context omitted.
My company has been self hosting the CE edition for quite a while; it's been totally smooth. Zero issues.
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.
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.
Earlier quoted context omitted.
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.
Dang. 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.
Relevant: https://docs.gitlab.com/ee/install/requirements.html#hardwar...
Earlier quoted context omitted.
Dang. 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.
Code 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#hardwar...
Changing that URL from "/ee/" to "/ce/" gives the same RAM requirements.
Earlier quoted context omitted.
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.
Dang. 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.
Earlier quoted context omitted.
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.
Dang. 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.
...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. :)
Earlier quoted context omitted.
Code 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#hardwar...
Thank 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.
Earlier quoted context omitted.
This is just utterly wrong. yum upgrade Done. No problems for years now. Not a single one.
Are you using it? I've yet to come across anyone hosting their own gitlab instance that has not had trouble of some sort.
I'm actually surprised that many people you know have had issues with it.