Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Poll: Self Hosting Git Repositories

news.ycombinator.com

Post reply on HN
Print view View original

81–86 of 86 posts

Re: Poll: Self Hosting Git Repositories

#81

Post by DoctorDabadedoo »

sieabah wrote: post #71
DoctorDabadedoo wrote: post #48

Earlier quoted context omitted.

Gitea is love. There are not a lot of shenanigans and it just does the job. If you want vcs with an online interface it's great for personal use and smaller teams. If you want fancier stuff like integrated CI/CD that is more common out there, Gitlab is an option, but running it by yourself it's not as simple (as gitea), for example.

Gitlab is extremely simple to run yourself. I've been doing it for 2 years at this point. What is really difficult about the operation?

Not really difficult per se, but more of anecdotal experience of needing dedicated time to maintain it internally. In a smaller company a few years back, whenever an update was due we would have some down time after it and someone had to spend a morning checking the server/dependencies/configs, this was around 2016.

Apart from that, a fact is that gitea is less resource hungry, so it runs well even in modest configurations.

Re: Poll: Self Hosting Git Repositories

#82

Post by saurik »

teekert wrote: post #80
saurik wrote: post #79

Earlier quoted context omitted.

git clone teekert@ssh.example.com:path/like/scp If you also want public access over http you can activate one of the default hooks (so a single "rename a file" command on the server) and then export it using literally any web server software (as it is a folder of dumb files).

Ah! Somehow I was assuming some magic in the cloning, some server-client relation. There is not I guess, and that is actually logical. Also refreshing in a way.

FWIW, I do believe that you have to have git installed on the other side, and what it is doing at an implementation level is using ssh to run a transient copy of the git daemon backed by that path on the remote machine, which communicates over stdin/stdout--and so over ssh--and which implicitly (due to the EOF) dies when the ssh connection dies. Like, I don't think it is accessing the remote side using mere scp/sftp file-system operations or anything (which would be horribly slow for a number of basic operations and would make cleanly running triggers and the such more annoying).

Re: Poll: Self Hosting Git Repositories

#83

Post by teekert »

saurik wrote: post #82
teekert wrote: post #80

Earlier quoted context omitted.

Ah! Somehow I was assuming some magic in the cloning, some server-client relation. There is not I guess, and that is actually logical. Also refreshing in a way.

FWIW, I do believe that you have to have git installed on the other side, and what it is doing at an implementation level is using ssh to run a transient copy of the git daemon backed by that path on the remote machine, which communicates over stdin/stdout--and so over ssh--and which implicitly (due to the EOF) dies when the ssh connection dies. Like, I don't think it is accessing the remote side using mere scp/sftp…

Thanx for this reply!

Re: Poll: Self Hosting Git Repositories

#85

Post by stillbourne »

I run gitlab on my kube cluster and installed that via helm charts and configured the omniauth system to communicate with my keycloak server via oidc. Overall complexity 6/10 took about 5 hours to fuss with it the first time. Subsequent deployments became easier. I hear Gitea is also a good selfhosted solution and less complex to install. However, I went with Gitlab specifically because we use it at work and I want to practice gitops/devops with it.

https://docs.gitlab.com/charts/installation/

Post reply on HN