Docker Swarm Stack

This repository contains the configuration of a Docker Swarm stack for self‑hosted services (reverse proxy, certificates, etc.) in a Home / Small Office environment.

Goals

• Centralize infrastructure configuration (services, volumes, secrets, networks).
• Enable reproducible deployments on a Docker Swarm cluster.
• Clearly separate responsibilities between infra, apps, data, and secrets.

Project structure

• infra/: infrastructure services (for example nginx, certbot, network configuration, etc.).
• apps/: application definitions and configuration (apps.yml files, init scripts).
• data/: initialization files (SQL, scripts) and persistent configuration for services.
• secrets/: text files containing secrets (passwords, keys, etc.).
  These files are ignored by Git (see .gitignore) and must not be versioned.

Prerequisites

• Docker installed (version compatible with Docker Swarm).
• Access to one or more Swarm nodes with the paths mounted as defined in the *.yml files (for example /home/ubuntu/docker/swarm/...).
• DNS configured to point to the reverse proxy (for example nginx + certbot).

Quick deployment (example)

1. Initialize the Swarm (if not already done):

   docker swarm init
   

2. Create Docker secrets from local files (adapt names as needed):

   docker secret create turn_secret secrets/turn_secret.txt
   docker secret create postgres_password secrets/postgres_password.txt
   # etc. for the other secret files…
   

3. Deploy the infra layer (reverse proxy, certificates, etc.) from infra/infra.yml:

   docker stack deploy -c infra/infra.yml infra
   

4. Deploy other services / applications using apps/apps.yml and data/data.yml (commands to adapt to your organization, for example multiple stacks).

Testing and validation

This repository mainly contains infrastructure configuration.
To validate your changes:

• Check YAML syntax (docker compose config, YAML linters, etc.).
• Deploy to a test environment and verify that Swarm services start correctly (docker service ls, docker service logs …).

Security

• Never commit real secrets into the Git repository.
• Use files in secrets/ only as local sources to create docker secret.
• Restrict read permissions on the secrets/ directory as much as possible.

More information

For more detailed documentation, examples, and operational notes, see the project wiki:
Server swarm wiki