Recommended use
The repository's active UAT workflow targets a Coolify-managed VPS. The small profile is designed around roughly 2 vCPU and 8 GB RAM for UAT/light workloads; use the full-scale profile or separate services as load grows.
Network layout
Expose only HTTP/HTTPS publicly through the reverse proxy. Keep PostgreSQL, Redis, and internal application service ports private. Restrict SSH to trusted administrators and protect the Coolify console with MFA.
Coolify resource
Use the repository branch and compose file configured for the environment. The current runbook uses docker-compose.coolify.yml and a health path of /health.
Pin immutable image tags for releases. GitHub Actions builds images and can trigger the Coolify deployment webhook after tests pass.
Persistent resources
Never recreate or casually rename production database, Redis, or application-storage volumes. Take and validate a backup before migrations or infrastructure changes.
After deployment
Run migrations once, sync/check product modules, optimise Laravel, restart Horizon, then test login, queues, storage, Flow forms/exports, Campaign sync, and dashboards.