Docker Compose, volumes and service lifecycle
Prerequisites and authority
Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.
Understand the deployment layout
Docker Compose defines the services and their relationships. Containers are replaceable execution units; persistent volumes and bind-mounted files hold data that must survive their replacement.
The inspected release Compose file declares MySQL, API, admin, customer website, Telegram bot and separate workers. API depends on healthy MySQL; other application services depend on API health. This dependency arrangement does not prove every background job is making progress.
| Storage | Inspected purpose |
|---|---|
bryannet-mysql-data |
MySQL files mounted at /var/lib/mysql |
bryannet-release-state |
Release/update state |
bryannet-report-storage |
Generated reports |
| Backup bind mount | Encrypted backup files, host destination configurable |
Installation .env |
Deployment configuration and sensitive values |
Use the actual installed paths. From its Docker directory, inspect configuration without displaying resolved secrets:
docker compose --env-file ../.env -f compose.release.yaml config --services
docker compose --env-file ../.env -f compose.release.yaml ps
PowerShell also accepts forward slashes for these relative file paths. Missing environment variables mean the selected files or environment are wrong; do not recreate services until configuration is corrected.
A normal service restart causes an interruption but should preserve mounted data. Recreating a container is different from deleting a volume. Never add -v to a production teardown as routine maintenance. Inspect mounts before any storage operation and use Back up BryanNet and validate backups/Restore BryanNet safely for backup and recovery.
Related guides
Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.