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
I'll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea's For-Profit owners
Silly question but what is the problem with gitea being for profit?
I guess out of fear that we get another gitlab situation, where the open source offering has a load of key features eventually kept behind a paywall
At some point they will do a Redis or Terraform and say no more open source, pay us to use it.
All contributions are now owned by us and not by the person who wrote it.
As the other commenter already said it's an abundance of caution. GItea is already moving in the direction of SaaS and an easily self-hostable solution runs counter to that plan (Gitea is already offering a managed Cloud so this is not a hypothetical). One thing that has already happened is Gitea introducing a Contributor License Agreement, effectively allowing them to change the license of the code at any time.
Well I learned something new today.. maybe its time to plan a migration
I think for now Forgejo is a drop-in replacement. However since they are a hard-fork, at some point in the future they will diverge enough to be mutually incompatible, so the clock is ticking on migrating.
From what I have read on the FAQ they already did a hard fork from Gitea version 1.21.11 on, which was earlier this year
https://forgejo.org/faq/#im-sold-are-migrations-from-gitea-to-forgejo-possible