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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
For the file server conundrum, something to keep in mind is that Proxmox is not NAS software and isn't really set up to do that kind of thing. Plus, the Proxmox devs have been very clear about not installing anything that isn't absolutely necessary outside of Proxmox (on the same machine).
However, you can set up a file server inside an LXC and share that through an internal VLAN inside Proxmox. Just treat that LXC as a NAS.
For your *arr stack, fire up an exclusive VM just for them. Install Docker on the VM, too, of course.
If you're gonna use that, please make sure you comb through the output and understand it before implementing it.
I was able to follow what you said with another comments yt video. I appreciate it. The LLMs were more of just a “explain this to me in simpler terms” or “why doesn’t this work” just cause I was tired after working most the time. it helped but it was also months ago with limited time to record much.
This absolutely overkill, just use bind mounts for the arr stack and keep the ZFS pool local.
Hardly. Keeping the file server separate is good for reliability in case you bork an unrelated service, so you don't take out everything else with it. That's also partly why things like VMs, LXC, and Docker exist.
??
Why would borking another service break a bind mount?
No need to be antagonistic. I merely suggested the method I use for my home lab after learning the "hard way" to containerize and separate certain things.
I'm not being antagonistic, I don't known where you're getting that.
Do what you want, I don't care.
On the other hand, I've been mounting my storage drives on the proxmox host with mergerfs and exposing what I need to the LXCs with bind mounts for years, and I haven't had a single issue with it across multiple major version upgrades.
That’s really solid actually. Arguably how tedious was that setup? I’m certainly curious.
Super simple, like 30 minutes to setup mergerfs and then the bind mounts are a few lines added to the LXC config files at most. This isn't necessarily needed, but I have users setup on the proxmox host with access to specific directories that are kind of a pain in the ass to remap the LXC users to, but were needed to give my *arr stack access to everything needed without giving access to the entire storage pool. Hard links won't work across multiple bind mounts because the container will see them as separate file systems, so if your setup is /mnt/storage/TV, /mnt/storage/downloads, etc. then you'd have to pass just /mnt/storage as the bind mount.
There you go, that's another option.