You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To debug data as it flows through your pipeline, use the `--log-payloads` flag:
52
+
53
+
```bash
54
+
moose dev --log-payloads
55
+
```
56
+
57
+
This logs payloads at three key points with searchable prefixes:
58
+
-`PAYLOAD:INGEST` - Data received at ingest API
59
+
-`PAYLOAD:STREAM_IN` - Data before streaming function
60
+
-`PAYLOAD:STREAM_OUT` - Data after streaming function
61
+
62
+
All logs appear in Moose logs and can be viewed using `moose logs --tail`.
63
+
49
64
### Extending Docker Infrastructure
50
65
51
66
You can extend Moose's Docker Compose configuration with custom services by creating a `docker-compose.dev.override.yaml` file in your project root. This allows you to add additional infrastructure (databases, monitoring tools, etc.) that runs alongside your Moose development environment.
Starts a local development environment with hot reload and automatic infrastructure management.
43
43
```bash
44
-
moose dev [--mcp] [--docker]
44
+
moose dev [--mcp] [--no-infra] [--log-payloads]
45
45
```
46
46
-`--mcp`: Enable or disable the MCP (Model Context Protocol) server (default: true). The MCP server provides AI-assisted development tools at `http://localhost:4000/mcp`. See [MCP Server documentation](/moose/mcp-server) for details.
47
-
-`--docker`: Use Docker for infrastructure (default behavior in dev mode)
47
+
-`--no-infra`: Skip starting docker containers for infrastructure
48
+
-`--log-payloads`: Log payloads for debugging data flow
0 commit comments