From 9b1c7b4d48004caa79788a5ac87c904cc8ad6439 Mon Sep 17 00:00:00 2001 From: jzhao234 Date: Wed, 16 Sep 2026 05:12:00 +0000 Subject: [PATCH 1/2] docs: the branding block also brands the Auth service 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. --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index a4988dc..21de7e3 100644 --- a/README.md +++ b/README.md @@ -166,6 +166,17 @@ 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`), From 90c0300ce0cf9690cde7aa1e838bc166b48a2334 Mon Sep 17 00:00:00 2001 From: jzhao234 Date: Wed, 16 Sep 2026 16:16:50 +0000 Subject: [PATCH 2/2] docs: keep the tab-title paragraph separate from the Auth note --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 21de7e3..49cee59 100644 --- a/README.md +++ b/README.md @@ -177,6 +177,7 @@ 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`),