Tutorials
Follow seven ordered lessons from one safe output event to forms, artifacts, scheduling, secrets, callbacks, and optional cloud infrastructure. The links below expose the exact maintained source used by the repository gate.
Start with Tutorial 01. Tutorials 01 through 04 need no secret value or cloud account. Tutorial 07 is optional and can create billable GCP resources.
Hello World
Build one Development Image, bind its verified managed digest to one Cookbook step, run it, and receive one safe lemc.output event.
- Time
- 20 minutes
- External cost
- None
- Cleanup
- Remove the test App and archive the image and Cookbook.
Forms and environment
Submit typed public form data, read its mapped environment values, and prove that LEMC rejects a reserved LEMC_ variable before a job starts.
- Time
- 20 minutes
- External cost
- None
- Cleanup
- Remove the test App and archive the lesson objects.
Streamed output and artifacts
Materialize buffered HTML, write one task-scoped artifact, reconnect to the durable event stream, and download the same bytes.
- Time
- 25 minutes
- External cost
- None outside local LEMC storage
- Cleanup
- Remove the task artifact and lesson objects.
Timing
Run separate now, in, and every phases, inspect their task identities, and cancel or replace scheduled work.
- Time
- 25 minutes
- External cost
- None
- Cleanup
- Cancel delayed and recurring work before archiving.
User secrets
Declare one disposable secret by name, prove missing-value preflight, bind it through the write-only catalog, and run without exposing the value.
- Time
- 25 minutes
- Secret
TUTORIAL_DISPOSABLE_TOKEN, supplied at runtime only- Cleanup
- Disable the disposable secret and archive the lesson objects.
Callbacks and cleanup
Observe page and recipe callbacks, fixed replacement order, retained cleanup state, and one retry of the exact failed cleanup snapshot.
- Time
- 35 minutes
- External cost
- None
- Cleanup
- Replace the active recipe and confirm terminal cleanup.
Optional cloud infrastructure
Opt in to one small GCP VM, record exact resource evidence, and prove teardown through a scheduled limit and an explicit destroy action.
- Time
- 45 minutes
- External cost
- GCP charges can apply
- Cleanup
- Run the exact destroy recipe and verify that the project inventory is empty.
Use a disposable project, one least-authority service account, one approved source /32, and a current budget alert. Never use an owner credential.
Source and safety contract
- The published files are a byte-for-byte projection of Git-tracked source under
examples/tutorials/. - Untracked files, internal fixtures, local state, and secret artifacts are not published.
- Cookbook YAML declares secret names only. It contains no secret value.
- Public authors use the Web application and LEMCSSH through stock OpenSSH. They do not need the internal native client.