Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 12, 2025

Users attempting wash dev ./flowmark-deployment.yaml encounter confusing errors because wash dev expects 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 files
  • wash 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-reload
  • wash dev ./deployment.yaml ❌ Fails - "Project path is not a directory"
  • No documented way to start wasmCloud host

The distinction between component development (wash dev) and cluster operations (wash host) was not clear from existing documentation.

Original prompt

wash dev ./flowmark-deployment.yaml
2025-11-12T12:56:47.425787Z INFO starting development session for project path="./flowmark-deployment.yaml"


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Start development session for flowmark deployment Document wash dev and wash host usage expectations Nov 12, 2025
Copilot AI requested a review from cdmurph32 November 12, 2025 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants