Allow configuring shutdown order and grace period for Coolify-managed services (Redis, PostgreSQL, etc.)

[mpenchenat93]

Hello,

I would like to request a new feature in Coolify regarding shutdown behavior for managed services.

Feature request: Allow configuring shutdown order and grace period for Coolify-managed services (Redis, PostgreSQL, etc.)

Currently, when deploying a service through docker-compose, we can use stop_grace_period to ensure a clean and graceful shutdown. This works perfectly for my NestJS API.

However, for “ready-to-use” services provisioned directly by Coolify (e.g., Redis, PostgreSQL), there is no option in the UI to configure a shutdown grace period or a shutdown order.

Why this matters

My application uses NestJS + Redis + PostgreSQL, and I have BullMQ queues consuming jobs continuously. These jobs frequently write to Redis and PostgreSQL.
During a server reboot, I want to guarantee that:

1. NestJS stops first (so it stops consuming jobs),
2. then Redis and PostgreSQL shut down only after a configurable delay,
3. so that active jobs can finish their processing safely without corrupted state.

On my VPS, reboots are necessary quite often (system updates), so a reliable shutdown sequence is important to avoid inconsistent states or job crashes.

What would be helpful

• Ability to define a grace period (like stop_grace_period) for Coolify-managed services.
• Ability to define a shutdown order, ensuring that application containers stop before their dependencies.

This feature would make Coolify much more robust for applications using queues, workers, and databases.

Thank you for considering this improvement!