this post was submitted on 12 Oct 2024
144 points (98.6% liked)

Open Source

31218 readers
256 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

And why?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 89 points 1 month ago (3 children)

Forgejo, a Gitea fork used by Codeberg. I chose it because it's got the right balance of features to weight for my small use case, it has FOSS spirit, and it's got a lovely package maintainer for FreeBSD that makes deployment and maintenance easy peasy (thanks Stefan <3).

[–] [email protected] 3 points 1 month ago

I do the same. Forgejo works really well, and I'm also absolutely stoked for forge fed some day.

It also has things like CI/CD. It's a really really good project and self hosting it is relatively painless. Even integrating it with my identity provider over oidc was no problem.

[–] [email protected] 5 points 1 month ago

+1 for Forgejo. I started on Gogs, then gathered that there had been some drama with that and Gitea. Forgejo is FOSS, simple to get going, and comfortable to use if you're coming from GitHub. It's actively maintained, and communication with the project is great.

[–] [email protected] 19 points 1 month ago (2 children)

I’ve been meaning to switch over from Gitea to Forgejo for ever. I’ll get it done tomorrow ;)

[–] [email protected] 1 points 1 month ago

Why switch from Gitea to Forgejo, if I may ask?

[–] [email protected] 15 points 1 month ago* (last edited 1 month ago)

Definitely best to get that done ASAP. Forgejo being a drop-in replacement for Gitea won't be guaranteed ever since the hard fork:

To continue living by that statement, a decision was made in early 2024 to become a hard fork. By doing so, Forgejo is no longer bound to Gitea, and can forge its own path going forward, allowing maintainers and contributors to reduce tech debt at a much higher pace, and implement changes - whether they’re new features or bug fixes - that would otherwise have a high risk of conflicting with changes made in Gitea.