Does setting "statics" on machine-level instead of app-level have any sense?

We can set [[statics]] for a web application to be served directly. And if I get it correctly, the fly proxy serves these statics somehow. This is a fantastic feature!

I have seen on the Machines API docs that we can also set statics per machine. I’d like to know the difference between this and setting it on the app with the fly.toml.
Here is why I’m interested: I use nginx to route traffic to the correct machine using a proxy_pass directive with the private_ipv6 of the target machines. To my understanding, there is no fly proxy between my nginx and the target machines. Is there any sense in adding the static section to my target machines?

Sorry for pushing this one to prevent automatic closing. I am still curious about the machine-level “statics” configuration field.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.