I would love to see a forge that consists of composable components, self-host able with federated identities and maybe a few centralized indexers
The forge we deserve
11–20 of 57 posts
Re: The forge we deserve
#12The forge we deserve is the one that is built for jj and local review.
Re: The forge we deserve
#13I'm way more hopeful in a fully decentralized protocol like Forgefed* than some AT still-centralized thing. * https://forgefed.org/
Cool. It's been years since ForgeFed came out but it isn't anywhere nearly as federated as Tangled is. What gives?
No idea what went wrong with ForgeFed, yeah.
---
Edit:
> Cool. It's been years since ForgeFed came out but it isn't anywhere nearly as federated as Tangled is. What gives?
Just read your other comments. Sorry, but I must point out that it would be polite to disclose that you’re working on Tangled, especially when posting takes like this on a competitor technology.
Re: The forge we deserve
#14Whereas in the "forges" space, it seems Tangled drives federation forward much faster than the ActivityPub-based federation features of Forgejo/Gitea (which are progressing really slow).
Re: The forge we deserve
#15I'm way more hopeful in a fully decentralized protocol like Forgefed* than some AT still-centralized thing. * https://forgefed.org/
(but what I'd know, I thought this was about typography forges - didn't know there were also software forges...)
Re: The forge we deserve
#16What I like about (the idea of) ForgeFed is that it lets existing forges speak to each other.
In practice I probably just need Forgejo and GitLab to be able to speak to each other.
I believe the future of GitHub, for me, is to solve two problems:
- Discoverability for public open-source projects
- Backup since self-hosting is fragile long-term
So many times when I try to visit the source code of some package uploaded to crates.io, the self-hosted git no longer exists.GitHub repos sit stale for decades.
For day-to-day reliance, my self-hosted Forgejo and CI runners have better uptime.
Only pet peeve with Forgejo:
- It's a highly active project, RFCs, tons of PRs and issues.
- Becoming a daily user, I want to extend it, and in its beautiful simplicity, it's not highly extensible.
- So to avoid maintaining a fork of a very active project, extending it in unison is a social commitment.
What a luxury problem, but still.I'd like to see more hosted Forgejo solutions pop up; it's very low-resource cost.
Re: The forge we deserve
#17I personally just self-host. The project that I'm working on right now uses Gitea internally with an action runner. I use Digital Ocean and run a Nomad cluster on top of that. Gitea and its action runner builds container images and then pushes nomad job definitions to the cluster. I have zero downtime deployment and rolling deploys. Dagger.io is in there somewhere to make local CI mirror what happens in the action ru…
While there are some problems with open source projects self-hosting their forges without federation, that’s really not the end of the world IMO (but lots of love for Tangled nevertheless).
Re: The forge we deserve
#18I'm pretty sure the actual forge we deserve at this point is one that is a membership organisation, eg, owned by its (paying) members. Members elect the board which chooses the CEO. A cooperative, in other words. The tech is a solved problem, with lots of open source around to do it. Enough members means paid operations and development staff, or outsourcing one or both, or grants to open source devs, etc. The possibi…
Like https://codeberg.org/? :-)
Re: The forge we deserve
#19Re: The forge we deserve
#20I personally just self-host. The project that I'm working on right now uses Gitea internally with an action runner. I use Digital Ocean and run a Nomad cluster on top of that. Gitea and its action runner builds container images and then pushes nomad job definitions to the cluster. I have zero downtime deployment and rolling deploys. Dagger.io is in there somewhere to make local CI mirror what happens in the action ru…
Codeberg runs on Forgejo (a Gitea fork) and is fairly big, so you’re in a good company. Maybe you’ll need to swap in another database, but SQLite is surprisingly powerful, too. While there are some problems with open source projects self-hosting their forges without federation, that’s really not the end of the world IMO (but lots of love for Tangled nevertheless).
Moved over from Sonatype Nexus to Gitea Packages as well since administering Nexus is annoying: https://docs.gitea.com/usage/packages
However for CI I use WoodpeckerCI (previously used Drone but migrated over), it works well with containers and is delightfully simple: https://woodpecker-ci.org/
Though I guess in my case I don't collaborate with others much outside of work, so it's just something to interact with across computers and servers.