A deployment now starts the side services its project declares, before the application
v0.23.0-beta
- A deployment now starts the side services its project declares, before the application. When a project has a managed cache or object storage, the compose file describes them, but deploying a container only started that container: the side service could exist nowhere. The application then started with an address nothing resolved, failed its health check, and the deployment was cancelled — without ever reaching the step that creates the project's nginx. Yet the reconciliation that could have caught up the side services is skipped precisely while that nginx does not exist: a fresh project using managed storage could no longer start at all. The agent now reads the compose file and starts the side services it lists before the application.
- Side services already healthy are not restarted on every deployment: they are simply checked present.
- The project nginx is still handled separately, as before: it is reconciled on its own so as not to interrupt the whole project on every single application's deployment.