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 hope you don't mind some questions.
I am curious about selfhosting an instance for a community but am afraid federation will consume too much time/resource/money for a side project.
No, I dont. The machine is wayyyy overspecced for these services, 6 cores, 16 GB of ram. What isnt overspecced is is the drive, 100 GB of nvme are fast but not enough for all my projects. I have taken a lot of measures to confine the services but mastodon is pretty much the worst offender afaik. Lemmy is the most intensive ram and cpu hog it has strong spikes every hour. You dont need six cores, two would most likely suffice. I think its a ryzen 5600 but not sure atm.
Average users are one each. A couple of friends have accounts but they dont usually use them. Federations is no big issue, single user instances could definitely be done from home, large instances should def be faster than my upload at least. Moving later is a pain so I‘d plan accordingly.
Maintenance is very hard if you do it manually, which I dont. Automate backups off site so a hack cant get the backups. Dockerize to hell and back, have fail2ban. Updates will break sometimes so make yourself familiar with docker and linux if you arent, otherwise you’re screwed as are your users. I‘d probably start with a solo server, then invite friends (beta testers) and then open to the public. You will also be defederated if you just open up to the public. Legal issues notwithstanding.
I hope this makes sense. Feel free to ask follow up question.