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
Makes sense. I think you’d be fine with pretty much any modern(post DDR4) motherboard/CPU combo these days. I feel Linux hardware support is only really shakey if you’re using a SoC without upstream patches or if you’re using brand new hardware/laptops. With that being said if you’re running a lot of containers on one host have you looked into docker compose or kubernetes(k8s)? Maybe k8s is overkill for home use, but both offer support to restart containers if a health check fails. With k8s you also can spread out containers across multiple physical node, so you could just add a second RPI and “double” your resources.
Also worth looking at k3s if its running on a single node to reduce resource usage