Install Basecamp.
Prepare the project environment before the task sandbox. Source stays separate; use your normal tools inside.
One project. One fixed target.
This runnable reference is the existing Rust / Cargo v0.5 path. It is not a universal language installer or a new SDK release. Prepare for a known target before handing the environment to the workload.
The recorded fixture supplies a bootstrap rustc for v0.5 native Cargo subprocesses, a system linker and a writable store. Those are explicit host prerequisites, not resources newly installed by this website.
curl -fsSL https://basecamp.sh/install.sh -o /tmp/basecamp-install.sh
# Review the installer before executing it.
sh /tmp/basecamp-install.sh1. Initialize the supported project once
On the connected preparation host, establish the environment identity from existing project files.
cd your-rust-project
basecamp init2. Reproduce the environment before the task
Sync materializes the selected environment. Keep this on the preparation side, not as an installer invoked by the final workload.
basecamp sync3. Deliver through the target’s supported route
Mount a target-host prepared store, create from a prepared image, or import an already materialized bundle. Source checkout stays independent. There is no invented universal “launch” CLI command in v0.5.
For the exact Docker example, use the published fixture and its README. Its preparation service, execution container, source delivery and entrypoint activation are separate.
docker compose run --rm prepare
# The fixture’s preparation service executes basecamp sync.
docker compose run --rm sandbox4. Activate in the actual task process
The fixture entrypoint sources the following environment file before its shell. A different route may use a different path. Source it in the same workload process; do not expect a setup shell export to reach all later sessions.
. /workspace/.basecamp/env
cargo test --offline --lockedNo pip/npm/runtime installation belongs in this step for the preprepared path. Tasks that need business APIs may still use the network under their own policy.
When the environment needs to change
basecamp status
basecamp doctor
# Re-resolve deliberately, back on the preparation host:
basecamp updateProve the boundary
Block dependency-source access, check startup actions, then run the actual task. A local UI “ready” state is not proof. Read the acceptance protocol.