starred/coolify
1
0
Fork 0
mirror of https://github.com/coollabsio/coolify.git synced 2026-11-06 21:18:11 -04:00
Code Issues Packages Projects Releases Wiki Activity

fix(service): delete resources from Coolify when server is unreachable

Browse Source 
DeleteResourceJob no longer restores a service and rethrows when remote
cleanup fails. The resource is always removed from Coolify, and the team
gets a notification that Docker resources may remain on the server. No
notification is sent when the server itself was already deleted.

removeSubresourceContainer now returns false instead of throwing when the
server is not functional. Deleting a service application or database then
shows a warning that the container is removed on the next service start.

StopService handles a missing destination server, environment, project,
or team without throwing. The danger zone warning now shows for any
resource whose server is unreachable, not only services.
This commit is contained in:
Andras Bacsai
2026-09-30 08:02:02 +02:00
parent 033f78d907
commit 2b5bffe37d
6 changed files with 99 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/views/livewire/project/shared/danger.blade.php
+4 -4
View File
@@ -8,11 +8,11 @@
default => 'resource',
};
@endphp
@if ($resource instanceof \App\Models\Service && !$resource->server?->isFunctional())
@if ($resource && !data_get($resource, 'destination.server')?->isFunctional())
<x-callout type="warning" title="Server is not reachable" class="mb-4">
Coolify cannot remove or verify Docker resources on this server. The deletion dialog will default to
removing this service from Coolify only. Its containers, volumes, networks, and configuration files may
remain on the server.
Coolify cannot stop or remove Docker resources on this server. Deleting removes this {{ $resourceLabel }}
from Coolify only. Its containers, volumes, networks, and configuration files remain on the server and can
start again when the server is back.
</x-callout>
@endif
<x-application.settings-section id="danger-zone-section" title="Danger zone"