9
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
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!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 4 years ago
MODERATORS
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.