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
1 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
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!
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
That will have a host of other issues that is not super fluid to work with while trying to maintain similar environments. Most notably the networking.
If this causes networking issues, your setup is already too complicated to manage through a flat set of docker containers. That's not a bad thing, this just isn't the horse for that course so to speak.
Not causing network issues, but for a layman that isn't familiar with managing multiple environments already, controlling a multi-env containerized environment is going to be a nightmare if solely just using containers as a staging environment. It doesn't map to what his prod env (non-container) would be, and it's not going to catch problems which would arise from his prod environment anyway if looking at from an integration standpoint.
I feel like that's a lot of assumptions based on OP's brief, but I don't disagree with anything you said.