coolify/app/Actions
Andras Bacsai 68a9f2ca77 feat: add container restart tracking and crash loop detection
Track container restart counts from Docker and detect crash loops to provide better visibility into application health issues.

- Add restart_count, last_restart_at, and last_restart_type columns to applications table
- Detect restart count increases from Docker inspect data and send notifications
- Show restart count badge in UI with warning icon on Logs navigation
- Distinguish between crash restarts and manual restarts
- Implement 30-second grace period to prevent false "exited" status during crash loops
- Reset restart count on manual stop, restart, and redeploy actions
- Add unit tests for restart count tracking logic

This helps users quickly identify when containers are in crash loops and need attention, even when the container status flickers between states during Docker's restart backoff period.
2025-11-10 13:04:31 +01:00
..
Application fix(application): increase docker stop timeout from 10 to 30 seconds for better application shutdown handling 2025-09-29 12:16:13 +02:00
CoolifyTask refactor(proxy-status): refactored how the proxy status is handled on the UI and on the backend 2025-06-06 14:47:54 +02:00
Database fix: remove debugging output from StartPostgresql command handling 2025-11-05 09:10:15 +01:00
Docker feat: add container restart tracking and crash loop detection 2025-11-10 13:04:31 +01:00
Fortify fix(user): ensure email attributes are stored in lowercase for consistency and prevent case-related issues 2025-09-05 17:44:34 +02:00
Proxy fix: streamline proxy status handling in StartProxy and Navbar components 2025-10-10 10:41:58 +02:00
Server feat: add dev_helper_version to instance settings and update related functionality 2025-11-03 08:38:43 +01:00
Service chore(deletion): rename isDeleteOperation to deleteConnectedNetworks 2025-08-04 22:12:04 +02:00
Shared fix(docker): enhance container status aggregation to include restarting and exited states 2025-09-18 18:12:52 +02:00
Stripe Changes auto-committed by Conductor 2025-10-16 17:13:47 +02:00
User Changes auto-committed by Conductor 2025-10-16 17:13:47 +02:00