Per-service Docker Deployment
The all-in-one stack puts every service in a single compose file. When you need to split them (e.g. admin web on an intranet, user web on a public network), deploy each sub-project with its own compose config:
| Directory | Contents |
|---|---|
server/docker/ | Backend service + Redis |
user-web/docker/ | User web + nginx |
admin-web/docker/ | Admin web + nginx |
Run in each directory:
bash
cd <sub-project>/docker
docker compose --env-file .env.prod up -d --buildDatabase initialization is the same as in the all-in-one deployment.
Previous: All-in-one Docker Compose deployment · Next: Bare-metal deployment