{{--
theme-admin no longer swaps the palette. It used to load a complete dark set
— its own surfaces, its own orange, its own status triad — which made the
console a second product and forced every shared component to work in two
worlds. It now carries density only: smaller type, tighter rows, tighter
corners. Colour comes from one place.
--}}
@php
$release = App\Services\Deployment\Release::current();
// Seeds the page-wide update watcher below. Computed here, once, for
// every console page — not only Settings — because the thing being
// watched restarts the containers serving whichever page the
// operator happens to have open, so the watcher (and its overlay)
// must already exist before that happens, wherever they are.
$updateChannel = app(App\Services\Deployment\UpdateChannel::class);
$updateState = $updateChannel->state();
$updateStep = $updateState['phase'] !== null
? __('admin_settings.update_step', ['step' => $updateState['phase']])
: null;
// The elapsed time and the deployment's raw output used to be read here
// and handed to the overlay. They are gone from it: neither is the
// question somebody staring at a maintenance screen has, and reading
// the log meant a file read on EVERY console page load, whether or not
// anything was running. The settings page still shows the log, where
// somebody is actually looking for it.
@endphp
{{-- "Bin ich im Test?" darf keine Frage sein, die man erst
durch Navigieren zur Integrationsseite beantwortet — die
Plakette steht im Kopf jeder Konsolenseite, solange der
Modus test ist, und verschwindet von selbst im Livebetrieb. --}}
@if (\App\Support\OperatingMode::current()->isTest())
{{ __('readiness.mode.test') }}
@endif
@auth
@endauth
{{ $slot }}
{{-- Maintenance overlay: the console during a deployment.
Bound HERE, once, rather than on the settings page's own update
card — this is the only binding of updateWatcher (resources/js/app.js)
in the app, so it is already in the browser, and stays in the
browser, no matter which console page the deploy catches the
operator on. Reported bug: the settings card flickered and vanished
mid-run, and every OTHER console page showed nothing at all, because
nothing was watching there.
Client-side is the only way this can work: the containers go down
mid-run, which is exactly when the view has to stay visible — a
server-rendered maintenance route cannot answer while it is itself
offline.
No close affordance: the run does not stop because an operator
closed a dialog, so offering one would be a lie. It clears itself —
window.location.reload() from inside updateWatcher — the moment the
build commit changes or `running` goes false, landing the operator
back on the very page they were on. --}}
{{-- The SAME panel the 503 page renders. It used to be a light card in
the app's own tokens, which meant an operator saw one design while
the application was still up and a completely different one the
moment the containers went down — two faces for one event, swapping
mid-update. The operator detail rides along inside it rather than
beside it. --}}
@include('partials.updating-panel', [
'body' => __('admin_settings.update_offline_hint'),
'detail' => true,
])