# hoody-watch Subskill ## Overview The `hoody-watch` service provides **file system watcher management** for Hoody containers. It monitors specified filesystem paths within a container and streams change events (create, modify, delete) in real time. ### When to Use - **Live reload workflows**: Watch source files and trigger rebuilds on change - **Configuration monitoring**: Detect when config files are modified at runtime - **Log tailing**: Stream file system events for operational awareness - **Development hot-reload**: Watch code directories during iterative development - **Audit trails**: Track filesystem mutations in production containers ### How It Fits Into Hoody Philosophy Hoody-watch follows the Hoody Kit service model: zero-configuration, container-scoped, and accessed through the standardized proxy routing pattern. Each watcher is bound to a specific container, ensuring isolation between projects and environments. All operations authenticate through the Hoody API — no direct filesystem access or SSH required. ### Key Concepts | Concept | Description | |---------|-------------| | **Watcher** | A persistent monitor on one or more filesystem paths inside a container | | **Event** | A filesystem change (create, modify, delete) detected by a watcher | | **SSE** | Server-Sent Events — one-way real-time stream from watcher to client | | **WebSocket** | Bidirectional real-time stream for watcher events | ### Service Endpoints | Method | Path | Description | |--------|------|-------------| | GET | `/api/v1/watch/health` | Service health check | | GET | `/watchers` | List all watchers | | POST | `/watchers` | Create a new watcher | | GET | `/watchers/{id}` | Get watcher details | | DELETE | `/watchers/{id}` | Delete a watcher | | GET | `/watchers/{id}/events` | List watcher events | | GET | `/watchers/{id}/events/sse` | Stream events via SSE | | GET | `/watchers/{id}/events/ws` | Stream events via WebSocket |