Document wash dev and wash host usage expectations #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users attempting
wash dev ./flowmark-deployment.yamlencounter confusing errors becausewash devexpects a project directory, not a deployment manifest. Additionally, there's no clear path for users who want to start wasmCloud locally.Changes
This PR addresses the documentation gap by clarifying:
wash dev- Expects a project directory containing buildable component source code, not YAML fileswash host- The command for starting a wasmCloud 2.0 host locally (requires NATS)Context
Current state:
wash dev ./my-component/✅ Works - builds and runs component with hot-reloadwash dev ./deployment.yaml❌ Fails - "Project path is not a directory"The distinction between component development (
wash dev) and cluster operations (wash host) was not clear from existing documentation.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.