Docs
RU

Ops & admin

uticms.operations · verified 2026-07-11

Overview

Scope
Filament administration, diagnostics, CORS, module assets, scheduler, and development-only routes

Key concepts

Admin Panel
The authenticated Filament administration surface guarded by the admin.panel middleware.
Resolved Features
The feature map published by CmsFeatures from frontend preset and overrides.
Module Asset
A file under a module Resources directory published to public/module/<slug> or served through the fallback controller.

Structure

  • Admin
    • Providerapp/Providers/Filament/AdminPanelProvider.php
    • Route Definitionsroutes/admin.php
    • Middlewareapp/Http/Middleware/AdminPanelMiddleware.php
  • Diagnostics
    • Serviceapp/Services/Cms/Diagnostics/SystemDiagnosticsService.php
    • Commands
      • cms:diagnose-site
      • page CMS diagnostic command
      • module discovery
      • module asset publication
  • Cors
    • Serviceapp/Services/Cms/Site/CorsConfiguration.php
    • Configurationconfig/cms.php

Facts

  • Admin routes include locale selection, two-factor setup/challenge, page and mail previews, and Editor.js upload. authoritative
  • AppServiceProvider schedules cache heartbeats for scheduler and queue diagnostics every minute. authoritative
  • When the default queue is not sync, the scheduled diagnostics heartbeat dispatches a queue job; sync queues write the heartbeat directly. authoritative
  • CMS CORS derives its mode from configuration and resolved public-CORS feature state; the headless preset enables public CORS while full and small leave it disabled. authoritative
  • Web and API development routes are available only in the local environment or when CMS_DEV_ROUTES resolves true. authoritative

How-to guides

Investigate Runtime Issue

  1. identify the relevant resolved feature gate and active-module state
  2. inspect application logs and the existing diagnostic service or command
  3. check scheduler and queue heartbeat state when background work is involved
  4. verify route middleware and CORS policy before changing public accessibility

Rules

Architectural rule

Change CORS through the configured policy and resolved feature flags rather than hard-coding per-route headers.