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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
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!
view the rest of the comments
Forgejo will follow next week: https://floss.social/@forgejo/110725896533944821
Why use that over gitea?
Currently? Zero reason.
Lummy, the creator of Gitea, wrote a post about why he moved Gitea over a company.
The TL;DR; is that it allowed Gitea to better work with companies that wanted to fund them but couldn't fund individuals directly, moved the Gitea trademark to an entity that could outlive the creator, etc.
There hasn't been any significant changes to how Gitea operates or can be used from a user point-of-view since the change happened.
Forgejo is a fork of Gitea that will pull changes made from Gitea, without being a company. In the events that Gitea goes to shit, it'll be there as a replacement.
Interesting read. Thanks for the extensive comment. I'm a bid baffled that I missed the announcement myself as I maintain the instance I use at work as our git reposity, main issue tracker, and internal package feed. So I try the follow the blog. But life is busy.
Forgejo is a community-run soft fork of Gitea created when Gitea became a corporation a couple months ago
The comments here have been the most measured and useful about this topic, glad you got great information that others can benefit from now.
Is the consensus to migrate to Forgejo or stay with Gitea? I’m running Gitea using docked and wondering how to migrate my setup to Forgejo, if needed.
I do not think there is a consensus. Personally, I am not moving anytime soon. IMO so far gitea has not done anything wrong yet (they just put them in a position where is easier for them to do it, eventually). It is still a good thing forgejo exists... but I can't stand the name, heh (also, I like the green theme of gitea :P).
Personally I am conflicted. On one side gitea switching to a for-profit is worrying, even if they didnt do anything wrong yet. I like codeberg (non-profit behind Forgejo), but I also want to support devs actually working on the product. So I think for now I'll stay with gitea, but I won't hesitate to migrate to Forgejo if they start to act stupid
It did not "switch to a for-profit". The company structure only exists to provide a way to hire gitea developers for paid work. The project owners are still elected by contributors: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#technical-oversight-committee-toc
For now. But n the long run the focus will shift to profit. That's a totally normal thing.
I switched to Fogejo just by swapping out the image. So far gitea hasn't been malicious with its trademarks now being owned by a private company, but I feel better using software that is more closely tied to a nonprofit. I see no reason to switch back.
Probably switching container from gitea to forgejo will just work… I recently switched my deployment, "issues" I had with postgres, but it was related to updates on helm-chart part (gitea upgraded postgres as well, so either update or switch made me same work to do).