mirror of
https://github.com/instructkr/claw-code.git
synced 2026-04-06 16:14:49 +08:00
Document a repeatable container workflow for the Rust workspace
Add a checked-in Containerfile plus container-first documentation so Docker and Podman users have a canonical image build, bind-mount, and cargo test entrypoint. The README now links directly to the new guide. Constraint: The repo already had runtime container detection but no checked-in Dockerfile, Containerfile, or devcontainer config Rejected: Put all container steps inline in README only | harder to maintain and less reusable than a dedicated guide plus Containerfile Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep docs/container.md and Containerfile aligned whenever Rust workspace prerequisites change Tested: docker build -t claw-code-dev-docs-verify -f Containerfile . Tested: cargo test --workspace (host, in rust/) Not-tested: Podman commands were documented but not executed in this environment Not-tested: Repeated in-container cargo test --workspace currently trips crates/tools PowerShell stub detection on this minimal image even though host cargo test passes
This commit is contained in:
@@ -31,7 +31,7 @@
|
||||
</p>
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The active Rust workspace now lives in [`rust/`](./rust). Start with [`USAGE.md`](./USAGE.md) for build, auth, CLI, session, and parity-harness workflows, then use [`rust/README.md`](./rust/README.md) for crate-level details.
|
||||
> The active Rust workspace now lives in [`rust/`](./rust). Start with [`USAGE.md`](./USAGE.md) for build, auth, CLI, session, and parity-harness workflows, use [`rust/README.md`](./rust/README.md) for crate-level details, and see [`docs/container.md`](./docs/container.md) for Docker/Podman container-first usage.
|
||||
|
||||
> Want the bigger idea behind this repo? Read [`PHILOSOPHY.md`](./PHILOSOPHY.md) and Sigrid Jin's public explanation: https://x.com/realsigridjin/status/2039472968624185713
|
||||
|
||||
|
||||
Reference in New Issue
Block a user