How-to
One task at a time: the steps for a job you already know you need to do.
| Article | What it covers | Updated |
|---|---|---|
| Observe a deployment | Where to look when something is wrong, and what each surface can and cannot tell you. Written for two people working on one box: the owner and whoever… | 2026-10-28 |
| Try the paid flow on this machine | The whole product runs in five containers on one machine: the relay, the control plane, Postgres, Caddy, and the docs site. This page walks the parts… | 2026-10-28 |
| Deploy a server | One small instance, one Docker host, one app container, six SQLite stores on one volume, Caddy in front, Cloudflare in front of Caddy. | 2026-10-28 |
| Operate a deployment | Suite runs as a single Node process with six SQLite stores on one directory; there is no external database and no multi-replica mode. | 2026-10-28 |
| Test and verify a change | Suite runs three test runners: Vitest for the workspace projects, Playwright for end-to-end journeys, and node –test for @suite/billing, which sits o… | 2026-10-28 |
| Change the canvas | Adding to the canvas means answering three questions before writing code: which layer owns the input, what the document records, and what peers see wh… | 2026-10-28 |
| Import an Obsidian vault | Importing a vault folder reads every note, tag, link and canvas into one workspace. The import runs once, as a single change, so undo takes it back wh… | 2026-10-28 |
| Release and roll back | A release is a tag, an image built from it on the host that serves it, the image id that identifies it, a smoke test against a host, and a rollback pa… | 2026-10-28 |
| Add a feature | The data flow fixes the order: the document package owns the shape, the workspace document owns the write, the snapshot store owns the read, and the c… | 2026-10-26 |
| Change the editor | Add a node, a mark, a field renderer, a slash command or a mention action to the card editor, with the files each one touches and the tests that fail… | 2026-10-26 |
| Contribute a change | One change, from branch to merge. The coding standards are in reference/conventions.md, the repo map in AGENTS.md, and the local gate in test-and-veri… | 2026-10-26 |
| Change the data model | A record change travels one path: schema, reader, writer, facade, then the tests that prove two clients still converge. Skipping the reader step is ho… | 2026-10-26 |