12 ms·
Self-hosting is king.
by rootnod3 1mo ago
Self-hosting is king.
- mschuetz 1mo agoExcept anything I'd self host would be down much more often. I've hardly ever actually experienced down time issues with github when I needed it.
- thecatapps 1mo agoI've never understood this argument. Even if self-hosted things were offline more often (which I've never found to be the case, I've had Forgejo + runners running for a year now with no downtime), the real benefit is that you yourself can work to bring it back online when it does, rather than waiting on a large, slow-moving organization to figure out what slopped PR caused their global service serving ungodly amounts of RPS to go offline again.
- onraglanroad 1mo agoI wrote my reply before yours appeared but it's basically agreeing. A simple Forgejo hasn't given me any grief. It really seems simpler. Maybe they're hosting in us-east-1 though :)
- crmsystems 1mo agolol
- Kinrany 1mo agoI don't follow, how is that better? It's down more often AND you have to do more work.
- thecatapps 1mo agoExcept it's not down more often and it's not a heavy lift. It's not a mail server, it's a Postgres database, a Golang app, and backups (and some providers will just handle that for you!).
- mschuetz 1mo agoBut I don't want to have to do this kind of work, you're only listing disadvantages from my viewpoint.
- thecatapps 1mo agoWhy? Like I wrote in a separate comment, it's not a mail server, it's a Postgres database, a Golang app, and backups (and some providers will just handle that for you!)
- mschuetz 1mo agoWhat do you mean "why"? Setting up and tinkering with systems is work I loathe to do, obviously. I want to code, not host coding repositories. I did it in the past because I had to, and now I don't have to do it because github does it for me. It's great.
- thecatapps 1mo agoExcept when Github’s down, of course. I’m saying it’s incomprehensible to me that people would rather put their trust into an organization as enshittified as Microsoft where they get their codebases added to an AI, have an awful experience (the code review UX, for example), and deal with consistent downtime, rather than put a few hours every so often into something that they loathe to do. That does not seem like a good trade-off at all.
- mschuetz 1mo ago> and deal with consistent downtime, Wildly exaggerated. I use github almost daily and can't remember when the last downtime was.
- thecatapps 1mo agoThis thread is about a nine hour outage in the middle of the east coast workday for Github Actions.
- jeltz 1mo agoThen you would be exceptionally bad at selfhosting as Github has like one nine of uptime.
- onraglanroad 1mo ago[dead]
- Nextgrid 1mo agoHard disagree. Self-hosting a service like GitHub that operates at GitHub scale is difficult. Self-hosting a service like GitHub that operates at the typical small/medium company's scale is trivial. A single machine (with separate runners for CI) will cover many companies' needs. It being a single machine eliminates a lot of the complexity and failure modes associated with a distributed system and makes backups/restores/maintenance easy.
- cautiouscat 1mo agoI’ve been self-hosting lore and gitea the past 6 months or so and it’s been a breeze. For anything I really care to share I throw up on Tangled.