|
tests / pest (push) Successful in 7m22s
Details
tests / assets (push) Successful in 24s
Details
tests / release (push) Successful in 4s
Details
Registering the console once per accepted hostname reused one set of route names, and Laravel refuses to serialise two routes under the same name — so `artisan optimize` failed on the live server the moment the separation was switched on, mid-deploy. Only the canonical registration carries the `admin.` names now; the alternates answer under `admin.viaN.*`. They exist to be MATCHED — they are the addresses someone locked out reaches for — never to have URLs generated for them, so route() keeps producing the canonical hostname. That renaming then broke every exact route-name check, which is how the console navigation decides what is active: reached through a recovery address, nothing in the sidebar was marked, exactly when something is already going wrong. The check goes through AdminArea now and matches either form. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| AdminConsoleTest.php | ||
| AdminHostRestrictionTest.php | ||
| AdminSettingsTest.php | ||
| ConsoleHostSeparationTest.php | ||
| ConsoleNetworkTest.php | ||
| ConsoleReportsRealDataTest.php | ||
| CustomerRevenueTest.php | ||
| DatacenterTest.php | ||
| HostManagementTest.php | ||
| InstanceAdminAccessTest.php | ||
| MaintenanceTest.php | ||
| PlanAdminTest.php | ||
| ProvisioningActionsTest.php | ||
| RbacTest.php | ||
| UpdateButtonTest.php | ||
| VpnTest.php | ||