Expand description
What the two dashboards this server serves do the same way.
docs/web-surfaces.md calls them surface 3 (crate::dashboard, the
operations page) and surface 4 (crate::analytics, the read-only
picture). They keep their own prefixes, their own routes and their own
files; what lives here is the plumbing underneath both: the tri-state
panel envelope, the operator session a control is reached behind, the
JSON refusal shape an API route answers with, and serving a static asset
under its content type.
Enums§
- Panel
State - The tri-state envelope every panel answers in.
Constants§
- CSRF_
HEADER - The header a mutating operator request must echo its session’s CSRF token in. A cookie rides along on a cross-origin form post; this does not.
- SESSION_
COOKIE - The cookie a signed-in operator’s browser carries.
Functions§
- acting_
operator - The DID this deployment’s operator signed in as, as the ledger records
an actor. Only reached behind
signed_in, which is what establishes that the caller controls it. - asset
- One static asset, served under
content_type. - html
- An HTML document.
- operator
- The operator sign-in, or a
503naming why this deployment has none. - refusal
- The
{"error": .., "message": ..}shape every route here refuses in. - script
- A script.
- session_
cookie - Reads
SESSION_COOKIEout of a request’sCookieheader. - signed_
in - Resolves a request to a signed-in session, or the refusal to answer with.
- stylesheet
- A stylesheet.