Configuration and Branding

Configuration and Branding

Most Rockdactyl settings are managed from Admin → Settings and stored in the database. Environment variables provide defaults for fresh installations.

Branding

Configure the panel name, footer owner and link, compact mark, optional logo, copyright start year, dashboard title, dashboard subtitle, and dashboard image. Use {username} in the subtitle to insert the signed-in username.

Local public assets belong under public/branding/ and are referenced with a path such as:

/branding/dashboard.jpg

HTTPS image URLs are supported when the remote host allows embedding. Only use artwork you own or have permission to distribute.

Theme Studio

Rockdactyl intentionally ships two complete presets:

• Crimson Red (makima) — the default warm crimson palette
• Midnight Blue (blue) — a cool blue alternative with the same components and behavior

Glass strength, card radius, and motion apply across client and admin views. Reduced-motion operating-system preferences override decorative animation.

Login and console media

Login and console background fields accept local public paths or remote HTTPS images. Console media also supports animated GIF, MP4, WebM, OGG, and MOV. Visibility controls keep terminal output readable, and background media never receives pointer input.

For console artwork, 12–24% visibility is a practical starting point. Verify long console lines and error output before increasing it.

Public status

The status page and node cards are enabled by default. When /status is public, its response includes aggregate health counts and can expose node IDs, names, health, and maintenance state. Use Summary Totals Only or hide node cards if node names are sensitive. It is a lightweight operator-controlled summary, not a replacement for external monitoring.

Global announcement

Announcements support notice, warning, and critical styles plus an optional internal or HTTPS action link. Keep messages brief. Never put secrets, internal addresses, or personal information in a public announcement.

Environment defaults

The complete list is maintained in configuration reference and .env.example. Database settings saved from the admin panel take precedence over those fallbacks.

Favicons

Replace matching files in public/favicons/, including favicon.ico, the 16 and 32 pixel PNGs, Apple touch icon, and android-chrome-192x192.png and android-chrome-512x512.png. Clear panel, proxy, and browser caches after changing them. Favicon URLs use the rock-red-2 cache token; bump it consistently in both Blade layouts, the manifest, and browserconfig.xml when you need to invalidate long-lived browser caches.