π Deployment Guide
FirstBreath is deployed on a VPS managed by Dokploy, an open-source alternative to Vercel/Heroku.
Infrastructure Overviewβ
We run multiple isolated Docker Compose stacks that communicate via a shared network.
How to Deployβ
1. Push to Masterβ
We use GitOps. Every commit pushed to the main branch of a repository triggers a rebuild in Dokploy (via Webhook).
2. Manual Deployment (Dokploy UI)β
If auto-deploy fails or you need a manual rollback:
- Log in to
https://dokploy.firstbreath.fr - Go to the Project -> Service (e.g.,
hub-api). - Click "Deploy".
Environment Variablesβ
Environment variables are managed in the Dokploy UI under the "Environment" tab of each service.
β οΈ Critical: Never commit
.envfiles. Always check Dokploy vars if a service fails to start in production.
Troubleshootingβ
"Bad Gateway" (502)β
Usually means the container is crashing or restarting.
- Check logs in Dokploy.
- Verify that the application is listening on the correct port (Backend: 3333, Frontend: 3000).
"Connection Refused" between servicesβ
Ensure both services are attached to the monitor-net external network in their docker-compose.yml.