mirror of
https://github.com/coollabsio/coolify.git
synced 2026-11-06 13:10:37 -04:00
Andras Bacsai
c6b8dfe367
After a start, the UI showed "exited" until the regular status check ran. That check runs on the shared high queue, which can be busy (60 s on Cloud). The start job (database) and the start task (service, on the deployment queue) now inspect only the started containers and store their status before they broadcast. While a health check reports "starting", they inspect again for up to about 15 s. ContainerStatusAggregator now builds the per-container status and the Compose aggregation for both writers, so GetContainersStatus and the targeted check store the same strings.
17 lines
367 B
PHP
17 lines
367 B
PHP
<?php
|
|
|
|
namespace App\Events;
|
|
|
|
use Illuminate\Foundation\Events\Dispatchable;
|
|
|
|
/**
|
|
* The remote process that starts a service (or one of its parts) finished.
|
|
* RefreshServiceStatusAfterStart stores the new status and broadcasts ServiceStatusChanged.
|
|
*/
|
|
class ServiceStartFinished
|
|
{
|
|
use Dispatchable;
|
|
|
|
public function __construct(public int $serviceId) {}
|
|
}
|