stephenway

I'm curious what you're replacing Actions with on the Forgejo side, and whether running that infra yourself feels like part of the benefit or another thing you'd rather not own

What makes it lightweight, and how does it boost your development over other saas solutions?

nice old.reddit.com, but I don’t think people want something as far back as 2015, they just want their forge to stay boring and fast

Curious what's driving the self-hosting discussion most, reliability, control, or compliance? Disclosure, I run a managed forgejo service

If you move the company too, what would make you pay someone to run forgejo instead of self-hosting it? Disclosure, I run Fjord, a managed dedicated forgejo provider.

This is a fair criticism of hosted Forgejo in general. Running Forgejo is the easy part. Backups, restore testing, upgrades, isolation and actually operating it for years are the product. Disclaimer, I run one called Fjord

once you add multiple users, bare git stops feeling "just" pretty fast. do you need reviews/CI too, or only shared access?

Forgejo is a great fit for what you're describing. I run Fjord, which is managed Forgejo. Our dedicated instances are above your $5-10 budget, but we also run a free public Forgejo instance if you want to try it without operating anything yourself.

I build Fjord, managed Forgejo with runners. The idea is to keep the GitHub-like workflow without having to operate the forge and CI infrastructure yourself.

This is exactly the migration problem we're trying to make boring with Fjord. It shouldn't require a flag day, bring up Forgejo alongside GitHub, mirror while the team moves over, then migrate CI incrementally.

For a 20–30 dev team I'd be happy to help work through what that rollout would actually look like

That's really good to hear, thank you. If you run into anything that's unclear while comparing the two, I'd genuinely like to hear it. Happy to answer questions here too.

This is pretty much why I started Fjord. I like Forgejo/Gitea, but didn't think “run your own forge forever” should be the only alternative to GitHub. We run dedicated Forgejo instances for people who want that middle ground.

Forgejo is probably worth a look if Actions compatibility and an easy migration are priorities. I run Fjord, a dedicated managed Forgejo, so you don't have to operate it yourself. We can help with the migration and runners too.

We also have a free public Forgejo instance if you want to try it first.

If you're seriously looking at Gitea/Forgejo, I run Fjord, dedicated managed Forgejo, so you don't have to operate it yourself. We can help with migration and runners too. We also run a free public Forgejo instance if you just want to kick the tires first.

what would make an alternative great enough to justify the move?

since you’re already on Blacksmith, how much of the remaining dependency is actions syntax vs GitHub itself?

what’s missing for you in Forgejo/GitLab/Gitea today? mostly the PR/review experience, or something else?

Would you move hosting/CI before Origin is available, or are you basically stuck on GitHub until then?

I think the interesting challenge isn’t running agents, it’s reviewing their work. The more code agents produce, the more important provenance, review ergonomics, and trust become. I also suspect repository platforms will need to evolve there over the next few years.

Un-entangled :)

Just released a new library so Sass users can now use Duo.js with duo-sass (https://github.com/stephenway/duo-sass). Check it out!

This is cool, works just as expected. I added in a designer news feed also so you can do both.