OpenRun console - todo flow walkthrough
Generated by TestTodoE2EFlow on 2026-11-02 16:33: overview → postgres service (secret url) → /bind/todo binding → /todo1 app (validate, then create) → console pages → overview. Each step is a light/dark screenshot pair; this page picks per your OS theme (`prefers-color-scheme`). 15 steps.
0101-overview
Overview home page: system status at a glance before the flow - apps, syncs, containers, services and recent activity.
0202-service-form
New service form: id postgres/tododb, the connection url locked into the secrets store ({{secret ...}} reference in the value field).
0303-bindings-service
Service created: postgres/tododb listed with its config key (the url value stays server-side).
0404-binding-form
New binding form: /bind/todo sourced from the postgres/tododb service. Creating it provisions an account on the database.
0505-bindings-populated
Bindings page with the service and the /bind/todo base binding.
0606-app-create-form
New app form: /todo1 from the github todo example, spec python-fasthtml, APP_MODULE=admin:app and the /bind/todo binding picked from the dropdown.
0707-app-validated
Validate (dry run): the source was fetched and checked, the permissions the app will request are listed for review.
0808-apps-list
Apps page with /todo1 created. No approval step was needed: the spec's permissions and the default postgres service's binding source are pre-allowed by the default server config.
0909-app-detail
App detail for /todo1: versions, requested permissions and the open-app links.
1010-containers
Containers page: the todo app's container is up.
1111-audit
Audit page: the create/approve operations recorded during this flow.
1212-syncs
Syncs page (declarative sources seeded by the suite).
1313-builder
App builder page.
1414-config
Configuration page.
1515-overview-final
Back on the Overview home page: the todo app shows in the apps tile's spec breakdown and its running container is counted in the containers tile.
→Embedding in the docs (hextra)
The docs theme toggles a dark class on <html>
(system preference included), so use the theme-image shortcode -
it follows the site's own toggle, which a plain
<picture>/prefers-color-scheme embed does not.
Copy the pair into docs/static/images/console/ and reference:
{{< theme-image light="/images/console/01-overview-light.png" dark="/images/console/01-overview-dark.png" alt="New service form" >}}