stephenway

Joined 14 years ago

Karma
16
Submissions
30
Member since
Jan 12
I build developer infrastructure. Currently building Fjord, managed dedicated Forgejo hosting.

Own your forge. Don't operate it.

https://fjord.sh

View on Hacker News

Recent submissions

Comment · 2 months ago
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
Comment · 2 months ago
What makes it lightweight, and how does it boost your development over other saas solutions?
Comment · 2 months ago
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
Comment · 2 months ago
Curious what's driving the self-hosting discussion most, reliability, control, or compliance? Disclosure, I run a managed forgejo service
Comment · 2 months ago
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.
Comment · 2 months ago
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
Comment · 2 months ago
once you add multiple users, bare git stops feeling "just" pretty fast. do you need reviews/CI too, or only shared access?
Comment · 2 months ago
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.
Comment · 2 months ago
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.
Comment · 2 months ago
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

Comment · 2 months ago
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.
Comment · 2 months ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton