2
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 27 Jun 2023
2 points (100.0% liked)
Self Hosted - Self-hosting your services.
11599 readers
17 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 3 years ago
MODERATORS
You can split services into multiple YAML files (i.e.
docker-compose.database.yml
anddocker-compose.backend.yml
or whatever) and then usedocker compose up -d docker-compose.database.yml docker-compose.backend.yml
. Compose treats this like it would one file internally (i.e. the services are connected to each other via an internal network by default).