From 9c8314e7a25f261a1134a32af22e44f2cc8b34d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Somhairle=20MacLe=C3=B2id?= Date: Tue, 5 Nov 2024 17:11:15 +0000 Subject: [PATCH 1/2] Update index.mdx --- .../runtime-apis/bindings/service-bindings/index.mdx | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx index a6e716aab24d4f..c0cfed03499cfc 100644 --- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx +++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx @@ -99,7 +99,16 @@ For more about the lifecycle of calling a Worker over a Service Binding via RPC, ## Local development -Local development is supported for Service bindings. For each Worker, open a new terminal and use [`wrangler dev`](/workers/wrangler/commands/#dev) in the relevant directory or use the `SCRIPT` option to specify the relevant Worker's entrypoint. +Local development is supported for Service bindings. For each Worker, open a new terminal and use [`wrangler dev`](/workers/wrangler/commands/#dev) in the relevant directory. When running `wrangler dev`, service bindings will show as `connected`/`not connected` depending on whether Wrangler can find a running `wrangler dev` session for that worker. For example: + +```sh +$ wrangler dev +... +Your worker has access to the following bindings: +- Services: + - SOME_OTHER_WORKER: some-other-worker connected + - ANOTHER_WORKER: another-worker not connected +``` ## Deployment From bf374a3ec6ca63339b3f780d286a4a97d5d40e44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Somhairle=20MacLe=C3=B2id?= Date: Tue, 5 Nov 2024 17:12:27 +0000 Subject: [PATCH 2/2] Update src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> --- .../workers/runtime-apis/bindings/service-bindings/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx b/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx index c0cfed03499cfc..4ac0e982f5233f 100644 --- a/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx +++ b/src/content/docs/workers/runtime-apis/bindings/service-bindings/index.mdx @@ -99,7 +99,7 @@ For more about the lifecycle of calling a Worker over a Service Binding via RPC, ## Local development -Local development is supported for Service bindings. For each Worker, open a new terminal and use [`wrangler dev`](/workers/wrangler/commands/#dev) in the relevant directory. When running `wrangler dev`, service bindings will show as `connected`/`not connected` depending on whether Wrangler can find a running `wrangler dev` session for that worker. For example: +Local development is supported for Service bindings. For each Worker, open a new terminal and use [`wrangler dev`](/workers/wrangler/commands/#dev) in the relevant directory. When running `wrangler dev`, service bindings will show as `connected`/`not connected` depending on whether Wrangler can find a running `wrangler dev` session for that Worker. For example: ```sh $ wrangler dev