deploy: mermaid flow diagram, single page with tabs, section rework

Collapse the deploy sub-pages back into one deploy.md (tabs, not separate
pages), add a working mermaid flow diagram, and rework the top per feedback.

- Mermaid: enable via superfences fence_div_format (the fence_code_format
  <pre><code> wrapper broke mermaid's render — div format fixes it); vendor
  mermaid.min.js locally (no CDN dependency for a self-hosted site) + a small
  init that renders each block once and survives instant-nav.
- Content tabs Compose / Dockerfile / Secrets hold the three pieces together
  on one page (inline comments in the code, no annotation +).
- 'What can run here' tip moved above the flow; section renamed
  'Preparing for Deploy' with the 'you don't run deploy commands' point folded
  sparsely into the intro (standalone note removed); 'svc never changes'
  called out.
- Flow diagram (below the tabs): build group now includes our libraries; git
  -> staging shown as develop-if-gitflow (dotted); deployment (no MR-to-main)
  -> docker image built + run on the fleet.
- Revert inbound links to deploy.md.

Verified in-browser: diagram renders with all nodes, tabs switch, section
order correct; mkdocs build --strict clean.

Signed-off-by: disqualifier <dev@disqualifier.me>

This commit is contained in:

dsql

2026-07-01 02:53:02 -04:00

parent f9e5e4f24d

commit 823aa7708a

12 changed files with 3837 additions and 282 deletions

									
										docs/environments.md
									
		+1
		-1
	
												View File
												
				@@ -67,7 +67,7 @@ happens, depending on where the project runs:

				    COPY . .

				    ```

				    This is how things run in production — see the [Deploy guide](deploy/) for the

				    This is how things run in production — see the [Deploy guide](deploy.md) for the

				    full container standard (uid 1337, the compose convention, layer caching, and the

				    uv image setup).