Tutorials
Follow six ordered lessons from one safe output event to forms, artifacts, scheduling, Providers, Secrets, and callbacks. 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 05 uses one disposable value and no external service.
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.
Providers and User Secrets
Create one Custom Provider Profile and one owner-qualified disposable Secret. Prove that only the Custom Provider guest receives plaintext. The separate recipe guest receives bounded YAML and read-only context.
- Time
- 30 minutes
- Secret
USERNAME/TUTORIAL_DISPOSABLE_TOKEN- Cleanup
- Disable the Cookbook Provider binding and the Secret; archive the Profile, Local Image, and Cookbook.
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.
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 one Provider and owner-qualified Secret pair. It contains no Secret value or binding.
- Public authors use the Web application and LEMCSSH through stock OpenSSH. They do not need the internal native client.