Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
view the rest of the comments
Gitea is not fundamentally different than Forgejo, Forgejo is just a better fork of it. Better in terms of: more contributors, more users, dogfooding (Gitea is built on Github ๐คฆ).
But yes, GitLab is like the Mac of Git forges: everything is included, doing everything their own way, vendor lock, very expensive. There is a community edition but serious users will run into its limitations and it does not integrate neatly with external solutions.
Forgejo is IMO the Linux of Git forges: low on resources, expandable, hackable, stable.
We should also keep in mind that Gitea was hostilely taken away from the community by a for-profit corporation that made Gitea open-core by hiding a way features behind a paywall in a cloud.
FUD
Gitea is still MIT licensed and the Enterprise tier features only cater to large org needs [1]. Why would I want to deal with nightmarish SAML config when OIDC does a better job
Forgejo was forked because the maintainers were butthurt they didn't have more say in the development roadmap and their large PRs didn't get reviewed and merged fast enough. Which is a valid reason to fork
No true Scot, then?
I'm running gitlab implementations at a few sites. I've not seen or heard of any performance limiter with a self-managed community edition that removes a tool the others still provide.
Again, this sounds FUDdy. Which 'external solutions' are you using that a git-push fails on? Some spaghetti of saas tendrils seems to be already a risk, but I can't think of any other external thing that it could mess up with.
Eh, there's not really a better/worse between Gitea and ForgeJo. Gitea is targeting business customers, ForgeJo is targeting the open source community.