Configuration & assets

Orbit configures itself lightly and lets the Panel instance carry brand and path. Assets are optional publishes.

Provider defaults

When OrbitServiceProvider registers, it seeds config if missing:

{
    "path": "/orbit",
    "font": "Outfit",
    "brand": "Orbit",
}

Prefer setting these on the panel — that’s the source of truth for the shell:

Panel.make("admin")
    .path("orbit")
    .brand_name("Acme Admin")
    .font("Outfit")
    .primary("#f1511b")

There is no published config/orbit.py file yet. When you need app-wide knobs, set app.config["orbit"] = {…} before boot or extend the provider.

Assets

Source	Published path	Shell URL
orbit.css	public/vendor/orbit/orbit.css	/vendor/orbit/orbit.css
orbit.js	public/vendor/orbit/orbit.js	/vendor/orbit/orbit.js

terminal

smith vendor:publish --tag=orbit-assets

orbit.js registers Alpine orbitNotifications data for flash rendering.

Prism directives

If Prism’s engine is bound, these directives are available:

@orbitStyles
@orbitScripts

They populate __orbit_styles and __orbit_scripts in the view context. The panel shell links the vendor URLs directly; use the directives when you embed Orbit chrome in your own layouts.

Middleware & auth

Panels default to the Almasix web middleware group (session, CSRF, cookies). Extra middleware appends:

panel.middleware(["auth"]).login().auth_guard("web")
# → ["web", "auth"]

Use .middleware([...], replace=True) only when you need to replace the whole stack. Orbit still gates guests via .login() — prefer not putting Almasix auth on the panel if you want the Orbit login page to stay reachable. Resource abilities still go through can_* helpers — see Resources.

Scaffolding

terminal

smith make:orbit-resource Post

The command is registered and accepts a name. File generation is still catching up — for now, copy the quick start resource and rename.