If only there was a convention for storing PRs and issues and wiki inside the repository itself, similar to how Fossil[1] does it. Then all the GitHubs and Gitlabs of this world would be limited to just providing UI and would be unable to hold our data hostage by design. [1] https://fossil-scm.org/home/doc/trunk/www/index.wiki
Ask HN: Alternatives to GitHub
111–120 of 468 posts
Re: Ask HN: Alternatives to GitHub
#112Re: Ask HN: Alternatives to GitHub
#113I self-host using my own read-only, FOSS, pure PHP Git repository reader for personal projects.
Re: Ask HN: Alternatives to GitHub
#114Re: Ask HN: Alternatives to GitHub
#115Happy to answer any questions.
Re: Ask HN: Alternatives to GitHub
#116Re: Ask HN: Alternatives to GitHub
#117https://tangled.sh
How easy is it to set up and run this for private repos? It looks like it has so many cool features -- stacked PRs, jujutsu support, CI in Nix VMs. But I've never tried it because it sounds like (at least by default) it's some sort of decentralized, peer-to-peer public thing
Re: Ask HN: Alternatives to GitHub
#118radicle.xyz to avoid centralization again
With Radicle you can continue to work locally with all issues etc intact, even if your “main” host is down. You can also sync through other hosts in the network.
Re: Ask HN: Alternatives to GitHub
#119Earlier quoted context omitted.
> depending on what you’re developing it may or may not be a good fit for you I think if your project is free / open source (edit: and you don’t use LLMs/AI), Codeberg is the a good starting point at least. You can move on to a self-hosted instance if you feel you’ve outgrown it, but even for larger projects I think you can get away with self-hosting just the CI runners. And don’t forget to donate! https://donate.cod…
if you use ai to program at all you can't use codeberg.
What you can't do is "share projects that mostly consist of code written by 'generative AI'-tools". https://codeberg.org/Codeberg/org/commit/71149c7fc95ccfeae36...>
Re: Ask HN: Alternatives to GitHub
#120I've used gitlab and gitea; gitea is faster, and easier to manage and does everything I actually need though, is less feature complete.
I'm one of the project leads of Gitea. I'd be interested in knowing which features you are missing from Gitea compared to Gitlab? We are doing some backlog grooming right now, and input is very appreciated:)