Removing [statics] from fly.toml has no effect

Questions / Help
#1

Hi,

I have removed the [[statics]] section from fly.toml since in my case it is more efficient to serve the files myself (to get better caching as they are immutable). I deployed more than half an hour ago but am still getting answers from the fly cdn. How long does it take to propagate removing the static “handler”.

Thanks,
Florian

Unable to turn off static asset caching
#2

This is a quirk with how our config logic interacts with toml. Removing the [[statics]] section entirely implies “no change” which keeps the old statics around. Try adding an empty [[statics]] section and deploying. This should push an empty list up and clear the config. Once that’s done you can remove [[statics]] and go on with life.

#3

Well that fails validation:

Error Statics [0] Url prefix can't be blank

when I solely have:

[[statics]]

in my fly.toml :&

#4

Agh! This is a known issue. For now, a workaround is to set your statics to a random, non-existent path:

[[statics]]
  guest_path = "/asdfasdf"
  url_prefix = "/asdfasdf"
#5

Thanks, that did work!