feat(login): configurable logo size + hideable heading/subtitle#521
Merged
rathlinus merged 1 commit intoJul 4, 2026
Merged
Conversation
Login header customization for white-label deployments, all defaults
preserve current behaviour:
- LOGIN_LOGO_MAX_HEIGHT / LOGIN_LOGO_MAX_WIDTH (any CSS length): the logo
box is otherwise a fixed 64x64 (w-16/h-16), which fits a wide wordmark to
~13px tall. When either is set, the fixed box is dropped and the logo
renders at the configured size.
- LOGIN_SHOW_HEADING / LOGIN_SHOW_SUBTITLE (default true): hide the
{appName} heading and/or the subtitle when the logo already reads as the
brand (e.g. a wordmark) and they'd be redundant.
Applied to the standard login header; wired through the existing config
registry (CONFIG_ENV_MAP) -> /api/config -> useConfig.
Refs bulwarkmail#519.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Login header customization for white-label deployments — three env knobs, all defaults preserving current behaviour:
LOGIN_LOGO_MAX_HEIGHT/LOGIN_LOGO_MAX_WIDTH(any CSS length, e.g.230px,3rem) — size the login logo.LOGIN_SHOW_HEADING(defaulttrue) — show/hide the{appName}<h1>.LOGIN_SHOW_SUBTITLE(defaulttrue) — show/hide the subtitle.Refs #519.
Why
Operators who brand with a wordmark logo hit two issues:
w-16 h-16,max-w-16 max-h-16), so a wide wordmark getsobject-contain-fitted to 64px wide → renders only ~13px tall (tiny). There's no setting for size.{appName}heading + subtitle are redundant when the logo already spells out the brand, but can't be turned off (the theme system is color-tokens-only, so CSS can't reach them either).We currently work around both by injecting
<style>at our reverse proxy, which couples to Bulwark's login DOM/classes and needs re-verifying on every upgrade.How
LOGIN_LOGO_MAX_HEIGHT/WIDTHis set, the fixedw-16 h-16box andmax-w-16 max-h-16are dropped and the configured max dimensions are applied inline; unset = unchanged 64×64.LOGIN_SHOW_HEADING/LOGIN_SHOW_SUBTITLEgate the<h1>/<p>.CONFIG_ENV_MAP→/api/config→useConfig), matching the surroundingLOGIN_*options. Applied to the standard login header (demo mode has its own header layout).Notes
LOGIN_SHOW_TOTP/LOGIN_SHOW_VERSION); independent branch, no overlap.npm run typecheck/lintin my environment, but this mirrors the existing config plumbing 1:1 — glad to adjust to conventions.