9
submitted 1 day ago by Campers@lemmy.world to c/selfhost@lemmy.ml

I am trying to plan my home lab to satisfy two different needs:

  1. I want a stable environment where I will put a relatively expensive NAS and maybe some other Zima boards.
  2. I also want to try new versions and configurations in an env where I can break stuff BEFORE trying things on my Production environment. I would also like to use that environment to try other things like playing with Kubernetes, Docker, Iceberg, etc. I am a backend software engineer so this is very useful to me. Besides being fun.

So, I am just trying to gather ideas on how to configure this both in terms of software and hardware.

you are viewing a single comment's thread
view the rest of the comments

Well the NAS itself isn't the integration point is what I'm saying, the data is, right? So have a folder on your NAS for staging, and another for production, and make the connection to that data the integration point that is accounted for in your dotenv or whatever you're planning on using to control this

The only downside there is the single point of failure being the NAS, but having two separated NAS boxes by environment won't solve for a production outage anyway because each environment still has a single point of failure even if you have two NAS.

Just get it running as above first. Figure out that actual breaking points in your flow after using it for awhile.

this post was submitted on 06 Apr 2025
9 points (90.9% liked)

Self Hosted - Self-hosting your services.

12522 readers
4 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 4 years ago
MODERATORS