Reframe Docker-centric wording so the conventional path is a first-class option Deployment-Basics.md's "What a deployment is made of" now opens with the substrate-neutral framing (conventional / Docker / Kubernetes all run the same base image and deployment-config), and "Running a deployment" leads with that same three-way framing before presenting the deploy-mf-<service> / scripts/start workflow as one way to bring a service up under Docker, pointing to the Cookbook and Deployment: Without Docker for the other two. Sweeps the rest of the wiki for the same assumption: Architecture-Advanced mentions systemd alongside Docker/Kubernetes for automatic restart and infra-component restart, and drops "container" as the implied only unit for per-instance role reporting, topology packaging, and the operational instance count. Configuration-Basics, Configuration-Advanced, and Deployment-Advanced add the conventional option alongside Docker/Kubernetes where a mounted-config or single-network example only named Docker. Configuration-Reference notes the Docker-free way to read the annotated defaults from an installation package. Image-Catalog and Cookbook-Enable- Tokens swap a couple of "container"/"in a container" phrasings for substrate-neutral wording. Glossary's Composition entry points at the Demo cookbook page instead of a no-longer-used "consolidated composition" name. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Cookbook: link to the actual subsections, not the page top The recipe links carried the #anchor on the display side of the wiki-link pipe, so the target had no fragment and every link landed on the page top. Convert the anchored cross-page references to markdown links (which honor fragments on GitHub wiki) and name the subsection in the link text, e.g. "Configuration: Advanced - Single sign-on" -> #single-sign-on-sso. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Add Cookbook section: Enable Tokens and Enable SSO recipes New task-oriented "how-to" section in the sidebar, after Configuration. Two thin, verification-led recipes - ordered steps plus links to the pages that own the detail, deliberately carrying no property names (the config surface self-documents, so recipes can't drift on key names): - Cookbook: Enable Tokens - /app/data on the primary, provision the store, first-boot bootstrap secret, mint the first admin token, issue tokens; verify with a 401-vs-Bearer probe and the self-report. - Cookbook: Enable SSO - drop SAML files into resources/rest.sso/, give the gateway the signing cert + allowed-origins, confirm the couplings, register the SP at the IdP; verify via the dashboard login bounce. Each recipe is its own page, so it appears as an individual sidebar link. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj