BryanNetDocker services, Compose files and persistent volumes
Prerequisites and authority
Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.
Services and persistent storage
The inspected docker/compose.release.yaml declares MySQL, API, administrator and customer web services, Telegram bot and dedicated workers. Exact service names are provided in the generated source table under this article.
MySQL uses the named bryannet-mysql-data volume at /var/lib/mysql. Release state and reports use separate named volumes. Backups bind mount BRYANNET_BACKUP_PATH, defaulting to the deployment-relative backups directory.
The database service is internal by default. The inspected support overlay temporarily maps 127.0.0.1:3306; it must not be generalized into public database exposure.
Use explicit deployment files and environment selection:
docker compose --env-file ../.env -f compose.release.yaml config --services
docker compose --env-file ../.env -f compose.release.yaml ps
Run from the installed Docker directory. config --services avoids dumping resolved secret values. A no-configuration-file error usually means the command was run elsewhere or without the selected -f file.
Compose declarations establish dependency startup and health checks, not a guarantee that queued work has completed. Worker progress remains a separate operational check.
Container removal/recreation and persistent-volume deletion differ. Keep the volume identity and database credentials consistent. Use Docker's volume reference for storage behavior and Restore BryanNet safely for recovery.
Inspected service inventory
| Service | Container | Runner/role |
|---|---|---|
mysql |
bryannet-mysql |
mysql |
api |
bryannet-api |
api |
subscription-worker |
bryannet-subscription-worker |
python -m app.workers.subscription_maintenance_runner |
organization-import-worker |
bryannet-organization-import-worker |
python -m app.workers.organization_import_runner |
integration-sync-worker |
bryannet-integration-sync-worker |
python -m app.workers.integration_sync_runner |
payment-worker |
bryannet-payment-worker |
python -m app.workers.payment_maintenance_runner |
router-worker |
bryannet-router-worker |
python -m app.workers.router_maintenance_runner |
network-sampling-worker |
bryannet-network-sampling-worker |
python -m app.workers.network_sampling_runner |
notification-worker |
bryannet-notification-worker |
python -m app.workers.notification_maintenance_runner |
report-worker |
bryannet-report-worker |
python -m app.workers.report_maintenance_runner |
analytics-snapshot-worker |
bryannet-analytics-snapshot-worker |
python -m app.workers.analytics_snapshot_runner |
release-update-worker |
bryannet-release-update-worker |
python -m app.workers.release_update_runner |
license-verification-worker |
bryannet-license-verification-worker |
python -m app.workers.license_verification_runner |
backup-worker |
bryannet-backup-worker |
python -m app.workers.backup_recovery_runner |
bot |
bryannet-bot |
python -m bot.main |
admin |
bryannet-admin |
admin |
customer |
bryannet-customer |
customer |
Related guides
Related guides: Configuration reference (env vars, ports, URLs), Database diagnostics and safe query reference, Subscription and provisioning state model.