Live data from Hacker News

Poll: Self Hosting Git Repositories

news.ycombinator.com

21–30 of 86 posts

Re: Poll: Self Hosting Git Repositories

#21
if it's for personal use and no access rights are needed, just use ssh.

If you need to add more people, but don't require access right for the git repos (i.e. everyone will be able to force push). Still use ssh, but create a git user and git-shell as the shell to improve security.

If you want to go one step up, I was looking at soft-serve, however it's too immature yet. So I added a git-shell-commands folder and added list command that will list my git repos.

It's really simple!

If you need access rights and reviews, things will be a bit more complicated. Although git-shell seems pretty easy to add some access rules to, if not gitolite is better. For browsing, cgit and gitweb should be obvious choices, however I don't really see the point for a minor site.

For code review, I'm really voting for git-appraise to take off. Once I get a coworker, that's what we will be using.

Re: Poll: Self Hosting Git Repositories

#22
post #18

Suggestion: Don't.* But, if you have your mind set: GitLab is great. (It WILL break at one point or another, and you will need to do recovery)

Hasn't broken for me, using it for a few years now. Are you talking of gitlab breaking specifically? Maybe that's the difference, since I use gitea instead.

Re: Poll: Self Hosting Git Repositories

#24
post #5
post #2

You may want to give more details about your usecase: do you need _only_ git hosting or other features too (e.g. issue tracker, CI/CD pipelines)? How many users will use this setup? Do you have a dedicated machine or you run it locally (e.g. in a docker container?? Hosting locally or in cloud? IIRC Gitolite was aquired by Gitlab a while back, Gitweb is not really a git hosting, it's more like a web view of your `git…

This poll is really me being curious about what the citizens of HN use themselves. My own use case would benefit greatly from CI/CD pipelines, but beyond that I'm mostly looking for a nice web interface to expose the repository contents.

[deleted]

Re: Poll: Self Hosting Git Repositories

#26
post #22
post #18

Suggestion: Don't.* But, if you have your mind set: GitLab is great. (It WILL break at one point or another, and you will need to do recovery)

Hasn't broken for me, using it for a few years now. Are you talking of gitlab breaking specifically? Maybe that's the difference, since I use gitea instead.

Self hosted gitlab breaks all the time, at least for us. Maybe had ~10 significant issues just the last few months.

Re: Poll: Self Hosting Git Repositories

#27
You may also want to include onedev [1][2] in your exploration (https://code.onedev.io/) if you also need good CI/CD integration.

My experience (as a user) has been pretty good, though I was not involved in the adminstration/setup related aspects but I have been told it doesn't require a lot of maintenance effort.

[1] https://github.com/theonedev/onedev [2] https://code.onedev.io/

Re: Poll: Self Hosting Git Repositories

#28
I used to use a self-hosted instance of gitbucket:

https://github.com/gitbucket/gitbucket

That's a single .WAR file, running under Java which was nice and easy to get started with, and even has support for some trivial CI/CD actions. Unfortunately a sudden death of the docker container it was running with corrupted the internal database to the extent that it wouldn't restart. (All my repositories were fine, on-disk, but the issues and similar stuff was mangled beyond belief.)

At that point I realized that I didn't use the issues, or pull-request facilities except very very rarely, so I switched to using bare repositories on a remotely hosted virtual-server.

Re: Poll: Self Hosting Git Repositories

#30
post #10
post #5

Earlier quoted context omitted.

This poll is really me being curious about what the citizens of HN use themselves. My own use case would benefit greatly from CI/CD pipelines, but beyond that I'm mostly looking for a nice web interface to expose the repository contents.

Then you don't have too much of a choice: gitlab all the way :) We ran an gitlab instance for about eight years and it worked flawlesly[1] for a team of ~20, with quite a few active repos (i.e. constantly pushing), some of them being generously large, running several pipelines on most of them. PS: gitorious was aquired by gitlab, not gitolite. My bad. [1]: once we pumped up _LOT_ of RAM into it that is

I would not recommend Gitlab. It is slow and buggy.

I cannot disclose details (we are premium customer and the bug reports would disclose my employer and identity), but every second week our Gitlab integration is blocked by some real shitty bug. Most common thing: Gitlab has a feature we need, but its only usable via WebUI and the API endpoint is broken or lacking in necessary details. So we cannot automate things that are very manpower-intensive.

Post reply on HN