this post was submitted on 25 Aug 2024
38 points (97.5% liked)

Selfhosted

40306 readers
494 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I have a decent 2 bay synology, but want to put all my docker images/ VMs running on a more powerful machine connected to the same LAN. Does it ever make sense to do the for media serving or will involving an extra device add too much complexity vs just serving from the NAS itself. I was hoping to have calibre/home assistant/tube type services, etc. all running off a mini PC with a Ryzen 7 and 64gb ram vs the NAS.

My Linux knowledge is intermediate; my networking knowledge is begintermediate, and I can generally follow documentation okay even if it's a bit above my skill level.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 2 months ago

I personally have them be the same device, but I have a DIY NAS, so my specs are already way overkill for regular NAS duty (it's my old desktop PC).

Assuming your home network is fast, you should be fine to split them up. I personally designed my setup to make it easy to move things around should I decide to. I use Docker containers for everything, Caddy for TLS, and HAProxy set up at the edge to route based on domain, so moving a service to another device is just:

  1. copy relevant docker compose and Caddy config to new machine
  2. set up network mounts for anything the containers need
  3. point HAProxy (and my router DNS) to the new address
  4. test

I don't have to remember where any of the config files are since they all live next to the compose file. I also don't need to forget which directories need to be mounted because it's already listed in the compose file.

So as long as you make it easy for yourself to move things around, it really doesn't matter where your actual data lives.