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:
- 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'm essentially doing this with my set up. I have a box running proxmox and a separate networked nas device. There aren't really any changes, per se, other than pointing the *arr installs at the correct mounts. One thing to make note of, i would make sure that your download, processing, and final locations are all within the same mount point, so that you can take advantage of atomic moves.
I second this. It took me a really long time how to properly mount network storage on proxmox VM's/LXC's, so just be prepared and determine the configuration ahead of time. Unprivilaged LXC's have differen't root user mappings, and you can't mount an SMB directly into a container (someone correct me if i'm wrong here), so if you go that route you will need to fuss a bit with user maps.
I personally have a VM running with docker for the arr suite and a separate LXC's for my sambashare and streaming services. It's easy to coordinate mount points with the compose.yml files, but still tricky getting the network storage mounted for read/write within the docker containers and LXC's.