Skip to content

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

Merged
jzhao234 merged 2 commits into
mainfrom
docs/auth-branding-note
Sep 16, 2026
Merged

jzhao234 merged 2 commits into
mainfrom
docs/auth-branding-note

Conversation

@jzhao234

Copy link
Copy Markdown
Contributor

TLDR

The Auth service (ElcanoTek/auth, password mode) reads the same branding: block Fleet does when AUTH_CLIENT_CONFIG_DIR points at a bundle. The README now says so, so a client bundle forked from this template reproduces the branding of both services from one manifest.

Fix

  • Branding section: one paragraph naming the fields Auth consumes (app_name, login_title, login_tagline, logo, colors), that nothing extra is needed in the bundle, that Auth refuses to start on an unreadable bundle, and the -check-config step. Links to auth's DEPLOY.md.

Tests

Docs only; no code changed.

The Auth service now reads the same `branding:` block Fleet does when its
`AUTH_CLIENT_CONFIG_DIR` points at a checkout of this bundle. The README's
Branding section says so, lists the fields Auth consumes, and points at the
config check to run after a branding change, so a bundle forked from this
template reproduces both services' branding from one manifest.
@jzhao234
jzhao234 merged commit 68cff13 into main Sep 16, 2026
@jzhao234
jzhao234 deleted the docs/auth-branding-note branch September 16, 2026 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant