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

Leaving GitHub for Forgejo

jorijn.com

Post reply on HN
Print view View original

31–40 of 380 posts

Re: Leaving GitHub for Forgejo

#31

Post by zsoltkacsandi »

nemomarx wrote: post #27
zsoltkacsandi wrote: post #23

Earlier quoted context omitted.

I think decentralization is the wrong answer for what people really need: portability.

What's the portability blocker with git? It's pretty easy to pull your repo and clone it to a new server, and you keep your history and everything I thought.

Nothing. That’s why SaaS providers like GitHub start to build up features like GitHub CI to lock people in. You can easily move the repo, but moving your full CI has a real cost that businesses will take into account when they are considering to move anything.

What do you think, what is the business for GitHub in providing limitless private and public repo hosting?

Re: Leaving GitHub for Forgejo

#32

Post by jdw64 »

ses1984 wrote: post #20
jdw64 wrote: post #15

People constantly cry out for decentralization. In reality, however, most systems eventually end up centralized. Perhaps when people ask for decentralization, they are actually seeking a new center where they can become the new pioneers. It seems that when they feel they have no chance of winning under the existing rules, they use decentralization as a pretext to overturn the board.

If only you bothered to read the first line of the article, directly under the title: >I moved my code from GitHub to a self-hosted Forgejo

I did read it. What I meant is that trying to isolate oneself using alternative platforms often looks like chasing a new trend. The ultimate irony is that the sheer complexity of the author's setup—KVMs, weekly rebuilds, isolated networks—is exactly the kind of burdensome infrastructure people were running away from in the first place. To clarify, my point was that specifically mentioning 'Forgejo'rather than just a generic personal 'home server'makes it come across as acting like a trendsetter

Re: Leaving GitHub for Forgejo

#33

Post by ninjahawk1 »

Didn’t realize the Dutch government was rad until I read this.

Frankly, the modern internet as a whole is scary. Google has so much power, Github, Meta, etc., they all control such fundamental parts of society now and get to run free since they’re private companies. Not saying they should be government owned, that would drastically worse, but some more detailed oversight would be nice.

Re: Leaving GitHub for Forgejo

#34

Post by sc68cal »

I have also moved my git repositories to a self-hosted NUC. I have not yet bothered with a HTTP frontend to share it with the world, mostly because I don't want to provide AI scrapers with content and don't want to put the work in to block them.

It's a shame that all these companies that benefited from open source have poisoned the industry like this

Re: Leaving GitHub for Forgejo

#36

Post by dewey »

giancarlostoro wrote: post #2

Everyone seems to be leaving GitHub, and forgetting the entire spirit of what git is in my eyes. Git was always meant to be decentralized, the problem here is that all the tooling around git was centralized to GitHub because it was a cleaner experience, they scaled nicely, and were properly maintained. I would prefer to still see mirrors on GitHub that are auto-synched because I've seen projects for years either self…

I don't think anyone is forgetting that, but most people don't care that much about the decentralized part. They care about it being user friendly, free and for companies if it has all the enterprise features / SSO etc. that they need.

Re: Leaving GitHub for Forgejo

#37

Post by diath »

henrydark wrote: post #29

I now use syncthing for the .git directory, excluding HEAD file and a few others, between my few devices and a vps on hetzner. Most of git is append only immutable blobs - just sharing these between devices just works for me. "users" and authentication is handled by syncthing. I have pre and post hooks to make sure no device tries to change HEAD of branch owned by another device, just to be safe, be it hasn't been ac…

If you have a VPS that's always running, you can just use it as a git remote through SSH without moving things around or any third party software, just put the Git repo on the VPS and clone it via "git clone ssh://user@host/path". You get authentication, encryption and synchronization out of the box with just ssh/git.

Re: Leaving GitHub for Forgejo

#38

Post by Finnucane »

"The Dutch government's choice of Forgejo, not GitLab, was deliberate."

And since Gitlab seems to have looked over at what is happening at Github and decided, we want some of that, that was probably the right choice.

Re: Leaving GitHub for Forgejo

#39

Post by j-bos »

henrydark wrote: post #29

I now use syncthing for the .git directory, excluding HEAD file and a few others, between my few devices and a vps on hetzner. Most of git is append only immutable blobs - just sharing these between devices just works for me. "users" and authentication is handled by syncthing. I have pre and post hooks to make sure no device tries to change HEAD of branch owned by another device, just to be safe, be it hasn't been ac…

Super interesting, mind sharing your exclusions and hooks?

Re: Leaving GitHub for Forgejo

#40

Post by import »

eblume wrote: post #28
import wrote: post #14

I’ve moved to self hosted gitea a year ago running in my homelab and not publicly accessible. No https, registrations disabled and repos are not public. I’m thinking about making public instance and use it with https, but minimize the attack surface, any recommendations especially about gitea/forgejo?

Yup, I’ve done this. I use a fly.io proxy that runs nginx, fail2ban, and that forwards to my tailnet where Caddy resolves to the actual instance. It’s critical that you disable local registration - I have authentik (only available on the tailnet) as an IdP but you can also just disable reg after making your own account of course. I also have a robots.txt that disables some stuff like all the individual rendered git c…

Hey thanks for the answer and link to docs. I don’t use tailscale, it’s running in a NUC, accessible with wireguard for now. (Docker + 4 runners)

I try to keep things simple in the homelab and thinking only using fail2ban and caddy reverse proxy and expose it.

Package registry isn’t private by default and accessible with PAT. Or am I mistaken?

Post reply on HN