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
Deployment-Basics: drop internal repo path, reorder DNS before Running Points the Compositions bullet at the Demo cookbook page instead of the internal docker-compositions repo path, and moves "Setting up a DNS entry for your API Gateway" ahead of "Running a deployment" so the gateway is addressable before the walkthrough tells you to start one. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017aV4rcuYnv4rUf3adqG7gj
Add Deployment: Image Catalog page Catalog of the deployable images, worked back from the deploy-mf-* projects and grouped by role: client-facing query services, projectors (market-data feeds / reference data / computed content), control plane, platform infrastructure, and all-in-one/evaluation. No versions/tags, no compositions (those live in Architecture / Deployment). socrata projector marked forthcoming. Linked from the sidebar, Deployment: Basics, and the Glossary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Move release notes to the deploy projects; drop the wiki page Release notes are per-artifact and per-version - each deploy-mf-* project ships the notes for the version it delivers - so a single wiki page cannot coherently track them and would rot. Remove the Release-Notes placeholder and its sidebar entry; add a pointer in Deployment: Basics ("Staying current") noting that each deployment project ships its own release notes; inline the release-tag convention in JMS App Dev where it used to link the removed page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Wiki-wide: replace the AI-tell "shape" with topology/arrangement/etc. "deployment shape(s)" -> "topology"/"arrangement"; "two shapes of API" -> "kinds"; "the shape your script expects" -> "structure"; "canonical shape of a subscriber" -> "form"; "production-shaped" -> "production-grade". Spans Architecture: Advanced, Deployment: Advanced/Basics/Without-Docker, Glossary, REST API, and the SimpleSubscriber example. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Deployment: Advanced - author from the networking architecture doc Networking-centered: bind vs advertise and the three host moments; "no single public host" (advertisement is per-network - retires PUBLIC_HOST); flat vs segmented (opt-in via *_NETWORKS); the network variables + NetworkDefinition descriptor (Cidr / AdvertiseHost) + fail-loud; the gateway's separate host model; and deployment shapes by substrate (Eclipse, Docker host / bridged / macvlan-multihomed, Kubernetes) with a decision guide. Distilled to client-facing altitude from docker-compositions/docs/host-resolution-and-networking.md. Reconcile composition framing (Glossary + Basics) to "worked templates; Kubernetes is the production substrate" - drops the "not a production deployment" wording. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L52U3EycDjN8uLAYL79HJ9
Deployment: Basics - drop MetaFluent bake-and-publish aside
Deployment: Basics - document scripts/start --registry override (tracks IssueTracking#596)
Deployment: Basics - review edits (build/configure intro, topology para merge, Building heading, correct registry-selection wording)
Split out Deployment: Without Docker page; Basics keeps a short pointer; add to sidebar
Deployment: Basics - revisions per review (concepts, compositions abstraction, topology decisions, resources edits, templated run example, baking wording, without-Docker section, corrected config-merge upgrade)
Deployment: Basics - move DNS setup section up (after Running, before packaging)
Deployment: Basics - deployment-project model, running, baking, own registry, upgrades, gateway DNS
Scaffold Elastic MDS wiki: Home, sidebar, footer, page stubs for the full doc set