coolify/app/Events
Andras Bacsai e4810a28d2 Make proxy restart run as background job to prevent localhost lockout
When restarting the proxy on localhost (where Coolify is running), the UI becomes inaccessible because the connection is lost. This change makes all proxy restarts run as background jobs with WebSocket notifications, allowing the operation to complete even after connection loss.

Changes:
- Enhanced ProxyStatusChangedUI event to carry activityId for log monitoring
- Updated RestartProxyJob to dispatch status events and track activity
- Simplified Navbar restart() to always dispatch job for all servers
- Enhanced showNotification() to handle activity monitoring and new statuses
- Added comprehensive unit and feature tests

Benefits:
- Prevents localhost lockout during proxy restarts
- Consistent behavior across all server types
- Non-blocking UI with real-time progress updates
- Automatic activity log monitoring
- Proper error handling and recovery

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-03 10:30:12 +01:00
..
ApplicationConfigurationChanged.php feat(event): introduce ApplicationConfigurationChanged event to handle team-specific configuration updates and broadcast changes 2025-09-22 09:44:30 +02:00
ApplicationStatusChanged.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
BackupCreated.php fix(horizon): add silenced jobs 2025-07-12 14:44:32 +02:00
CloudflareTunnelChanged.php 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
CloudflareTunnelConfigured.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
DatabaseProxyStopped.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
DatabaseStatusChanged.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
DockerCleanupDone.php feat: DockerCleanupDone event 2025-01-15 17:19:32 +01:00
FileStorageChanged.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
ProxyStatusChanged.php 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
ProxyStatusChangedUI.php Make proxy restart run as background job to prevent localhost lockout 2025-12-03 10:30:12 +01:00
RestoreJobFinished.php feat: add validation methods for S3 bucket names, paths, and server paths; update import logic to prevent command injection 2025-11-25 16:40:35 +01:00
S3RestoreJobFinished.php feat: improve S3 restore path handling and validation state 2025-11-25 10:18:30 +01:00
ScheduledTaskDone.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00
SentinelRestarted.php feat(sentinel): implement SentinelRestarted event and update Livewire components to handle server restart notifications 2025-08-26 10:27:38 +02:00
ServerPackageUpdated.php feat(security): implement server patching functionality 2025-05-15 22:21:54 +02:00
ServerReachabilityChanged.php feat: new ServerReachabilityChanged event 2024-12-16 14:05:17 +01:00
ServerValidated.php work work on hetzner integration 2025-10-09 16:54:13 +02:00
ServiceChecked.php fix(horizon): add silenced jobs 2025-07-12 14:44:32 +02:00
ServiceStatusChanged.php refactore(core): use property promotion 2025-05-20 13:23:09 +02:00
TestEvent.php refactor(actions): standardize method naming for network and configuration deletion across application and service classes 2025-04-30 18:30:43 +02:00