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 went down a similar path as you. The entire proxmox community argues making it an appliance with nothing extra installed on the host. But the second you need to share data — like a nas — the tooling is a huge pain. I couldn’t reliably find a solution that felt right.
So my solution was to make my nas a zfs pool on my host. Bind mounting works for CTs but not VMs which is an annoying feature asymmetry. So I decided to also install an nfs server that exposed my nas.
I know that’s not what you want but just wanted to share what I did.
The feature asymmetry between CTs and VMs basically made CTs not part of my orchestration.