4 ms·

Why people self host a git site? If they're not an organization and are not looking for views, there aren't any reasons to self host.

cinericius 1y ago
They want to have control over where their code lives, and not have their code subject to the terms of the service of the platform they use. For example, I might want to host my code privately on GitHub and not have Microsoft use it to train their LLMs. That doesn't seem to be possible: https://github.com/orgs/community/discussions/135400 https://github.com/orgs/community/discussions/135400 https://github.com/orgs/community/discussions/171080 https://github.com/orgs/community/discussions/171080
snmx999 1y ago
I self-host a git site to keep my code private and to integrate an issue tracker. The maintenance effort is very low. I'm running Gitea on my local network Ubuntu server.
packetlost 1y ago
I self-host most of my personal git repos on a NAS. They're literally just `git init --bare` folders in `/srv/src` that I access over SSH. Requires essentially zero setup and maintenance and I don't have to be worried if my internet or some other provider dies.
- quectophoton 1y ago
  This also allows more freedom in the directory structure, instead of the `$USERNAME/$REPONAME` that is enforced by basically every hosted solution.
  - packetlost 1y ago
    Yup, though you actually lose the ability to control access via groups in the URI this way (not that it matters, it's way more flexible to use Unix FS permissions)
bayindirh 1y ago
I do some personal R&D and want to keep it under wraps until I'm ready to share it to the world. Keeping stuff on services you can depend is great for many things (I use SourceHut, btw.), but sometimes you want to have your code on-premises. This is not the next billion dollar business, but I don't want to share the code until I write a couple of papers on it, and anchor the code's and idea's provenance correctly. I had a softer stance on the issue, but since AI companies started to say "What's ours is ours, and what's yours is ours", I need to build thicker walls and deeper moats. No, it won't be permissively licensed if I open source this.
panny 1y ago
I would self host if I also wanted build actions, issues, wiki like Github/Gitea support. I believe the article is about this part. How do I collaborate with others without building a dependency on a tyrant? Gitea + Traefik + Keycloak + federated github login probably does the trick these days. It's been a while since I built a SDLC project.

cinericius 1y ago

They want to have control over where their code lives, and not have their code subject to the terms of the service of the platform they use. For example, I might want to host my code privately on GitHub and not have Microsoft use it to train their LLMs. That doesn't seem to be possible: https://github.com/orgs/community/discussions/135400 https://github.com/orgs/community/discussions/135400 https://github.com/orgs/community/discussions/171080 https://github.com/orgs/community/discussions/171080

snmx999 1y ago

I self-host a git site to keep my code private and to integrate an issue tracker. The maintenance effort is very low. I'm running Gitea on my local network Ubuntu server.

packetlost 1y ago

I self-host most of my personal git repos on a NAS. They're literally just `git init --bare` folders in `/srv/src` that I access over SSH. Requires essentially zero setup and maintenance and I don't have to be worried if my internet or some other provider dies.

quectophoton 1y ago
This also allows more freedom in the directory structure, instead of the `$USERNAME/$REPONAME` that is enforced by basically every hosted solution.
- packetlost 1y ago
  Yup, though you actually lose the ability to control access via groups in the URI this way (not that it matters, it's way more flexible to use Unix FS permissions)

bayindirh 1y ago

I do some personal R&D and want to keep it under wraps until I'm ready to share it to the world. Keeping stuff on services you can depend is great for many things (I use SourceHut, btw.), but sometimes you want to have your code on-premises. This is not the next billion dollar business, but I don't want to share the code until I write a couple of papers on it, and anchor the code's and idea's provenance correctly. I had a softer stance on the issue, but since AI companies started to say "What's ours is ours, and what's yours is ours", I need to build thicker walls and deeper moats. No, it won't be permissively licensed if I open source this.

panny 1y ago

I would self host if I also wanted build actions, issues, wiki like Github/Gitea support. I believe the article is about this part. How do I collaborate with others without building a dependency on a tyrant? Gitea + Traefik + Keycloak + federated github login probably does the trick these days. It's been a while since I built a SDLC project.