Skip to content

docs: the branding block also brands the Auth service #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jzhao234 merged 2 commits into from
Sep 16, 2026
Merged

docs: the branding block also brands the Auth service #32

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b1c7b4
docs: the branding block also brands the Auth service
jzhao234 Sep 16, 2026
90c0300
docs: keep the tab-title paragraph separate from the Auth note
jzhao234 Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,6 +166,18 @@ meaning, so a failed tool call reads as failure in every deployment.

Full reference: fleet's
[docs/BRANDING.md](https://github.com/ElcanoTek/fleet/blob/main/docs/BRANDING.md).

**The same block also brands the Auth service.** A client deployment that
uses central sign-in (the `auth` repo in password mode) points Auth's
`AUTH_CLIENT_CONFIG_DIR` at a checkout of this bundle, and Auth reads the
`branding:` block above — `app_name`, `login_title`, `login_tagline`, `logo`
and `colors` — for its sign-in, signed-in and admin pages. Nothing extra is
needed in the bundle: one manifest, one palette, both services. Auth ignores
the rest of the file and refuses to start on a bundle it cannot read, so run
`auth-server -check-config` after a branding change. See auth's
[docs/DEPLOY.md](https://github.com/ElcanoTek/auth/blob/main/docs/DEPLOY.md)
("Branding from the client bundle").

The browser **tab title** and PWA name follow `branding.app_name` too, but only
on a fleet at or past #899 (`f793c6e`, 2026-07-30): from there the web layer
resolves the name server-side per request (via the token-gated `/brand/meta`),
Expand Down