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
Keeping storage and compute separately is the best practice but if you're OK with combining both in one device then running docker-compose on a Synology (via SSH, + versions only) works just fine. An alternative that reduces the lock-in at the expense of more tinkering is buying an amd64 QNAP and installing Openmediavault / TrueNAS / plain Debian.
Perhaps I can delegate the RPI4 to handle storage and then do compute on a new NUC.
Why is it superior to keep them separate, if you don't mind me asking?
Not OP, but I'm running into some issues with my machine being both my "server" and my "NAS".
The biggest downside is that if I want to update my storage, I will also have to update the server, and viceversa.
Sometimes the server goes down for whatever reason (e.g., distro update), and I lose access to the storage as well.