this post was submitted on 27 Jul 2025
68 points (98.6% liked)
Selfhosted
59905 readers
567 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IMO, the Gogs dev was correct. If you look at that community input and what Gitea became, I was glad to use the version that rejected it.
But I don't know how it compares with Forgejo.
It’s Gitea with some security fixes and community input, as open source software should be.
what's the problem with gitea? I never used gogs so I can't compare it
The added features made it harder to deploy, came with some bugs, and overall traded a simple design for community-oriented features that IMO were a negative value overall.
made it harder to deploy? Isn't it still just a single binary, a config file and a directory for data?
bugs are inevitable for evolving software.
which community oriented features do you mean? are they in the way, or is it just that you don't need them?