Skip to content

Document local-only website bootstrap canonical URLs #61

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
shiny-code-bot merged 1 commit into from
Jun 12, 2026
Merged

Document local-only website bootstrap canonical URLs #61

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion docs/tooling/tenant-overlay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,8 @@ When
- tracked `workspace.toml`
- tracked `artifact-inputs.toml` for runtime and publish-time source inputs
- tracked `website-bootstrap.toml` when the tenant needs Launchplane/devkit to
rebuild public website identity, canonical URL, homepage route, or logo state
rebuild public website identity, local canonical URL, homepage route, or logo
state
- tenant-owned code

## Tenant Root Should Not Contain
Expand Down
10 changes: 6 additions & 4 deletions docs/tooling/workspace-cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,10 +182,12 @@ Notes
supported addon settings such as `authentik_sso` values.
- When a tenant repo contains `website-bootstrap.toml` beside `workspace.toml`,
runtime selection also folds that non-secret website intent into the same
typed payload. The bootstrap contract can add install modules, select the
lane canonical URL, identify a homepage page or controller route, and point at
a repo-local logo asset. Data workflows and startup apply that state
idempotently after modules are installed, without hard-coded tenant defaults.
typed payload. The bootstrap contract can add install modules, provide the
local canonical URL, identify a homepage page or controller route, and point
at a repo-local logo asset. Shared/testing/prod canonical URLs are
Launchplane-owned runtime records. Data workflows and startup apply bootstrap
state idempotently after modules are installed, without hard-coded tenant
defaults.
- Legacy setting-shaped inputs such as `ENV_OVERRIDE_CONFIG_PARAM__*`,
`ENV_OVERRIDE_AUTHENTIK__*`, and `ENV_OVERRIDE_SHOPIFY__*` are still accepted
as a compatibility input and converted into the same typed payload, but they
Expand Down