HomeAboutMailing ListList Chatter /0/0

Gitlab has become a pig...

2019-11-26 by: Michael Harrison
From: Michael Harrison 
 In the process of upgrading, I also upgraded GitLab to version 12.x. Now
all that thing does in churn and thrash. My server is constantly running a
1-2 load, and it's all ruby,redis,sidekiq.. etc..

Does anyone elses do this, or have I fubared gitlab? It seems to be working

Anyone know of a basic usage git server management interface, suitable for
2-5 users and a dozen simple projects,

My two other choices are running a straight up git server or building a
minimal web interface for git.


=============================================================== From: Lee Walker ------------------------------------------------------ I've not upgraded to v12 yet, but GitLab has been great for me so far. The previous upgrades were really simple and easy, and went well. I'll update mine soon, and let you know how it goes. But I love GitLab, I use the crap out of it. Git, project management, CI/CD etc. Nice that it's all in one tool and one interface. Also I've not heard about any problems like that from others. On Tue, Nov 26, 2019, 7:53 AM Michael Harrison wrote:

=============================================================== From: William Roush ------------------------------------------------------ SeKAmXZlIGJlZW4gZGViYXRpbmcgbW92aW5nIHRvIEdpdGxhYiBmcm9tIEdpdGVhLCBidW1tZXIu IEkgaG9wZSB0aGF0IGNsZWFycyB1cC4NCg0KSSBnZW5lcmFsbHkgbGlrZSBHaXRlYSBidXQgaXQg ZmFsbHMgc2hvcnQgaW4gYSBmZXcgcGxhY2VzIGFuZCBoYXMgc29tZSBuYXN0eSBidWdzLg0KDQoN CldpbGxpYW0gUm91c2ggfCBodHRwczovL3d3dy5yb3VzaHRlY2gubmV0Lw0KT2ZmaWNlOiA0MjMu OTMzLjIxMTQgfCBDZWxsOiA0MjMuNDYzLjA1OTIgfCBFbWFpbDogd2lsbGlhbS5yb3VzaEByb3Vz aHRlY2gubmV0PG1haWx0bzp3aWxsaWFtLnJvdXNoQHJvdXNodGVjaC5uZXQ+DQoNCg0KDQpGcm9t OiBDaHVnYWx1ZyA8Y2h1Z2FsdWctYm91bmNlc0BjaHVnYWx1Zy5vcmc+IE9uIEJlaGFsZiBPZiBN aWNoYWVsIEhhcnJpc29uDQpTZW50OiBUdWVzZGF5LCBOb3ZlbWJlciAyNiwgMjAxOSA3OjU0IEFN DQpUbzogQ2hhdHRhbm9vZ2EgVW5peCBHbnUgQW5kcm9pZCBMaW51eCBVc2VycyBHcm91cCA8Y2h1 Z2FsdWdAY2h1Z2FsdWcub3JnPg0KU3ViamVjdDogW0NodWdhbHVnXSBHaXRsYWIgaGFzIGJlY29t ZSBhIHBpZy4uLg0KDQogSW4gdGhlIHByb2Nlc3Mgb2YgdXBncmFkaW5nLCBJIGFsc28gdXBncmFk ZWQgR2l0TGFiIHRvIHZlcnNpb24gMTIueC4gTm93IGFsbCB0aGF0IHRoaW5nIGRvZXMgaW4gY2h1 cm4gYW5kIHRocmFzaC4gTXkgc2VydmVyIGlzIGNvbnN0YW50bHkgcnVubmluZyBhIDEtMiBsb2Fk LCBhbmQgaXQncyBhbGwgcnVieSxyZWRpcyxzaWRla2lxLi4gZXRjLi4NCg0KRG9lcyBhbnlvbmUg ZWxzZXMgZG8gdGhpcywgb3IgaGF2ZSBJIGZ1YmFyZWQgZ2l0bGFiPyBJdCBzZWVtcyB0byBiZSB3 b3JraW5nIG9rLg0KDQpBbnlvbmUga25vdyBvZiBhIGJhc2ljIHVzYWdlIGdpdCBzZXJ2ZXIgbWFu YWdlbWVudCBpbnRlcmZhY2UsIHN1aXRhYmxlIGZvciAyLTUgdXNlcnMgYW5kIGEgZG96ZW4gc2lt cGxlIHByb2plY3RzLA0KDQpNeSB0d28gb3RoZXIgY2hvaWNlcyBhcmUgcnVubmluZyBhIHN0cmFp Z2h0IHVwIGdpdCBzZXJ2ZXIgb3IgYnVpbGRpbmcgYSBtaW5pbWFsIHdlYiBpbnRlcmZhY2UgZm9y IGdpdC4NCg0KLS1NaWtlLS0NCg0KDQoNCg0KDQo= X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQ2h1Z2FsdWcg bWFpbGluZyBsaXN0CkNodWdhbHVnQGNodWdhbHVnLm9yZwpodHRwOi8vY2h1Z2FsdWcub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby9jaHVnYWx1Zwo=

=============================================================== From: Adam Jimerson ------------------------------------------------------ I generally like GitLab, and happy to that they decided against rolling out the crazy 3rd party telemetry that would affect not only their SaaS offering but the locally hosted builds as well. I like having my SCM, CI, and ticketing system, project management all in one place. That said it does not hurt to have some alternatives on hand, and lucky Git makes migrating the repo near brain dead simple, the other stuff maybe not so much. That one alternative I have been playing with that is not resorting to running Git as a daemon with the GitWeb enabled, is SourceHut (https://meta.sr.ht/) which is built by a strong Open Source advocate Drew DeVault. It is written in Python and like GitLab can be used as a SaaS product or installed and managed locally. The way it is designed if running it locally you can turn certain bits of it off. Currently SourceHut supports the following: - Hosting unlimited Public and Private Git repos (https://git.sr.ht/) - Hosting unlimited Public and Private Mercurial repos (alpha support and not even listed on the nav bar currently but it is there) (https://hg.sr.ht/) - Build system for running CI and/or building release tarballs (https://builds.sr.ht/) - Issue tracker (https://todo.sr.ht/) - Hosted Mailing lists for your projects (https://lists.sr.ht/) - Wiki support (https://man.sr.ht/) - Automation and Integration support with other services (https://dispatch.sr.ht/) SourceHut itself is Open Source (https://git.sr.ht/~sircmpwn/) and has a minimal UI by design, the goal is the UI should still be 100% usable even with JavaScript disabled. There is a little oddity in its design where SourceHut does not follow the Pull/Merge Request trend, instead it follows the more traditional model used by the Git and the Linux Kernel devs where you email git patches (part of the reason why mailing list support is baked in). That said to end this "plug" which i am no way getting anything out of other than the joy of sharing a project I find neat If you want to have a look and how it looks here is a test repo I created on it https://git.sr.ht/~vendion/freebsd-ports P.S. Mike, by default Git already ships with a minimal WebUI https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb downside is it's a CGI script but one already exists and is actively maintained, your mileage may vary of course. On Tue, Nov 26, 2019 at 8:04 AM William Roush wrote:

=============================================================== From: Michael Harrison ------------------------------------------------------ a lot to read and digest and play with. Thanks. ut it t that

=============================================================== From: Dave Brockman ------------------------------------------------------ If you need something simple, I use gitolite3 and websvn for browsing. It's simple, but I don't need much, aside from the repos themselves, and the ability to view and compare files in them. Cheers, -Dave X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQ2h1Z2FsdWcg bWFpbGluZyBsaXN0CkNodWdhbHVnQGNodWdhbHVnLm9yZwpodHRwOi8vY2h1Z2FsdWcub3JnL2Nn aS1iaW4vbWFpbG1hbi9saXN0aW5mby9jaHVnYWx1Zwo=

=============================================================== From: Billy ------------------------------------------------------ I was helping a customer with an internal DevConf in Nashville with some other software. Their internal IT demanded that they be the ones to set up the gitlab instance in AWS. They chose the minimum requirements... for 300 simultaneous attendees - which gitlab was also performing the authentication and authorization. Which surprisingly is about 8 gigs and 2 cores. It fell over on itself midway through. Two shocking revelations: 1) always load test your infrastructure 2) Why TF isn’t 8 Gigs and 2 cores enough for OAUTH authentication for 300 people?? --b

=============================================================== From: Stephen Kraus ------------------------------------------------------ Gitlab has seemed to have moved to "We're an appliance and need our own host" method, unfortunately. p 0 n for 300 d