Skip to content

Commit 170e8af

Browse files
authored
[wrangler] Document new multiworker support (#18467)
1 parent 9272ea4 commit 170e8af

File tree

1 file changed

+9
-2
lines changed
  • src/content/docs/workers/runtime-apis/bindings/service-bindings

1 file changed

+9
-2
lines changed

src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,10 +124,17 @@ $ wrangler dev
124124
...
125125
Your worker has access to the following bindings:
126126
- Services:
127-
- SOME_OTHER_WORKER: some-other-worker connected
128-
- ANOTHER_WORKER: another-worker not connected
127+
- SOME_OTHER_WORKER: some-other-worker [connected]
128+
- ANOTHER_WORKER: another-worker [not connected]
129129
```
130130

131+
Wrangler also supports running multiple Workers at once with one command. To try it out, pass multiple `-c` flags to Wrangler, like this: `wrangler dev -c wrangler.toml -c ../other-worker/wrangler.toml`. The first config will be treated as the _primary_ worker, which will be exposed over HTTP as usual at `http://localhost:8787`. The remaining config files will be treated as _secondary_ and will only be accessible via a service binding from the primary worker.
132+
133+
:::caution
134+
135+
Support for running multiple Workers at once with one Wrangler command is experimental, and subject to change as we work on the experience. If you run into bugs or have any feedback, [open an issue on the workers-sdk repository](https://github.com/cloudflare/workers-sdk/issues/new)
136+
137+
:::
131138
## Deployment
132139

133140
Workers using Service bindings are deployed separately.

0 commit comments

Comments
 (0)