A disposable copy of the Compose services you pick.

Run your browser flows from your laptop against the tunnelled services and keep the video, screenshots and report. They can also run as a uses: cairntrace step of a ci: suite on the server, beside the app (cairn 3.x; the on-box toolchain is baked with chalupa snapshot build --toolchain onbox).

Evidence from ci: suite runs is uploaded and attached to the run. Failed laptop runs are stashed locally and fcheap restore <id> brings them back.

Beta: Laptop runs that pass are not attached to anything, and laptop evidence cannot be uploaded for the console to open (report.evidence.publish: cloud is refused today). Evidence stored in file.cheap cloud opens from the console run page; a laptop pack shows its restore command there.

Coming next: Upload laptop-run evidence for the console to open.

A failing step in a ci: run includes the stack trace and the culprit frame. With observability.crashCapture, any container death in the Compose projects you list is recorded on the box and shows in the console's issues page beside the CI ones.

Beta: It listens to Docker container deaths, so it needs Compose and covers only the projects you list; containers outside them are not covered. Host metrics work on one provider.

Reference ${NAME} in a service override and launch with tvault run --only NAME -- chalupa up.

Beta: Values are written to the server's startup config and to your local state today. env_file is not supported.

Coming next: Runtime delivery that never writes them there.

Logs of the Compose services you opt in with session.logs are collected as log chunks and shown as short excerpts in the console for 24 hours. A run page shows the excerpts that fall inside that run's window; chalupa logs reads a running box's logs directly.

Beta: Collection can stop at its chunk limit or the original deadline, and retention depends on your plan. A service with its own non-journald logging driver must be excluded, and containers outside your Compose file are not collected.

Coming next: Search across collected logs in the console.

Run history, a page per run, CI runs, issues and performance windows for the environments you link.

Beta: Log excerpts are short, only evidence stored in file.cheap cloud opens there, and the console shows what your environments report: it does not control servers.

The console shows one page per run: the failing step, the evidence attached to it, the logs and containers in that run's time window, and the cost of the window.

Beta: Evidence opens from the page only when it is stored in file.cheap cloud; a laptop run shows a restore command instead of the files, because uploading laptop evidence (report.evidence.publish: cloud) is still refused. Logs are short excerpts and need session.logs.