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
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ curl http://localhost:8600
202
202
203
203
## Remote dispatch namespaces
204
204
205
-
You can configure dispatch namespace bindings to connect to remote dispatch namespaces during local development by setting `experimental_remote = true`:
205
+
You can configure dispatch namespace bindings to connect to remote dispatch namespaces during local development by setting [`experimental_remote = true`](/workers/development-testing/#remote-bindings):
206
206
207
207
<WranglerConfig>
208
208
```jsonc title="wrangler.jsonc"
@@ -218,6 +218,6 @@ You can configure dispatch namespace bindings to connect to remote dispatch name
218
218
```
219
219
</WranglerConfig>
220
220
221
-
This allows you to run your [dynamic dispatch Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dynamic-dispatch-worker) locally, while connecting it to your remote dispatch namespace binding. This allows you to test changes to your core dispatching logic against real, deployed [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers).
221
+
This allows you to run your [dynamic dispatch Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dynamic-dispatch-worker) locally, while connecting it to your remote dispatch namespace binding. You can then test changes to your core dispatching logic against real, deployed [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers).
222
222
223
223
For more information about remote bindings during local development, refer to [remote bindings documentation](/workers/development-testing/#remote-bindings).
Copy file name to clipboardExpand all lines: src/content/partials/workers/bindings_per_env.mdx
+19-23Lines changed: 19 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,25 +8,25 @@ During local development, your Worker code always executes locally and bindings
8
8
9
9
You can configure [**remote bindings** during local development](/workers/development-testing/#remote-bindings), allowing your bindings to connect to a deployed resource on a per-binding basis.
10
10
11
-
| Binding | Local simulations |Remote binding connections|
-**Local simulations:** Bindings connect to local resource simulations. Supported in [`wrangler dev`](/workers/wrangler/commands/#dev) and the [Cloudflare Vite plugin](/workers/vite-plugin/).
32
32
@@ -58,8 +58,4 @@ Supported only in [`wrangler dev --remote`](/workers/wrangler/commands/#dev) - t
58
58
|**Vectorize**| ✅ |
59
59
|**Workflows**| ❌ |
60
60
61
-
[^2]: Using Hyperdrive with local simulations allows you to connect to a local database (running on `localhost`) but you cannot connect to a remote database. To connect to a remote database, use `wrangler dev --remote`.
62
-
63
-
[^4]: Analytics Engine is supported with local simulations in Wrangler but is not currently supported in the Vite plugin.
0 commit comments