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/workers/static-assets/binding.mdx
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
pcx_content_type: concept
3
-
title: Configuration and binding
3
+
title: Configuration and Bindings
4
4
sidebar:
5
5
order: 7
6
6
head: []
@@ -133,3 +133,13 @@ export default {
133
133
## Routing configuration
134
134
135
135
For the various static asset routing configuration options, refer to [Routing](/workers/static-assets/routing/).
136
+
137
+
## Smart Placement
138
+
139
+
[Smart Placement](/workers/configuration/smart-placement/) can be used to place a Worker's code close to your back-end infrastructure. Smart Placement will only have an effect if you specified a `main`, pointing to your Worker code.
140
+
141
+
:::note
142
+
143
+
Turning on Smart Placement in a Worker that is using static assets and [`serve_directly=false`](/workers/static-assets/routing/#invoking-worker-script-ahead-of-assets) means your entire Worker could be moved to run closer to your data source. All requests will go to that Worker before serving assets. This could result in an increase of round trip times when fetching assets through an asset binding.
0 commit comments