Vasyka/autocrm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

diag: distinguish Coolify provisioning failures (not configured vs API fail)

Browse Source
This commit is contained in:
Vasyka
2026-05-07 07:45:46 +00:00
parent 9192914de4
commit 2b4fa666ad
2 changed files with 20 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
app/Filament/Central/Resources/CompanyResource/Pages/CreateCompany.php
+3 -2
View File
@@ -18,9 +18,10 @@ class CreateCompany extends CreateRecord
$msg = "Admin: {$result['admin_email']}\nParolă: {$result['admin_password']}";
if ($result['deploy_triggered']) {
$msg .= "\nSubdomain adăugat în Coolify, redeploy declanșat (~90s).";
$msg .= "\n✅ Subdomain adăugat în Coolify, redeploy declanșat (~90s).";
} else {
$msg .= "\n⚠️ Coolify nu e configurat — adaugă manual https://{$result['company']->slug}.service.mir.md:8000 la FQDN-ul aplicației.";
$detail = $result['coolify_message'] ?? 'unknown';
$msg .= "\n⚠️ Provisioning automat eșuat ({$detail}). Adaugă manual https://{$result['company']->slug}.service.mir.md:8000 la FQDN-ul aplicației.";
}
Notification::make()