Skip to content
SHC Docs

Flows

Layer 11. Lifecycle. Layer page.

Step-by-step walkthroughs of the multi-stage pipelines in SHC. Each page traces the code end-to-end, citing the actual source files and line numbers; if the code changes, these pages are expected to drift and should be updated.

These are how it actually executes docs. For the conceptual contract of a subsystem, see the corresponding module page. For how to use a feature, see the operator guide or the app-development docs.

FlowWhat it covers
install.mdshc install: one render, stored, then the node starts from the spec
upgrade.mdshc update: the same render seam; a placement change relocates first
render-once.mdone stored render; the leader finishes it; the node does not render
failover.mdthe leader’s delivery of a stored render onto the node a bind named
uninstall.mdshc uninstall + ordered multi-deployment teardown (best-effort forward)
backup-restore.mdshc backup create and restore: restic path, local .bak path, restore pipeline
clone-move.mdrelocate (shc update --where), plus shc clone and shc rename
cluster-join.mdshc node token + shc node join: from bootstrap token to mesh-member
event-lifecycle.mdDocker event / audit event → SSE subscriber
authentication.mdEvery way identity is established: app-native SSO, the forward-auth gate, the launcher’s silent check, and the two edge auto-redirect mechanisms
launcher.mdThe injected apps menu: how it authenticates on an ungated host, the same-origin design that makes it work, and the third-party-cookie limit that bounds it
  • A module page (“what does app own?”) is a conceptual overview. Stable. Changes when responsibilities change.
  • A flow page (“what runs when you click install?”) is a procedural trace. Less stable. Changes when the pipeline changes.

Flow pages freely link back into module pages, security, and config references; they are the glue.