What is the preferred way to cache static files these days? (i.e.
ccs/js)
Recompile with slowfs module
Serve css/js through php backend and use fastcgi_cache
Create additional nginx localhost server and proxy_cache from nginx
backend
Drupal6 has a nasty habit of recreating its aggregated css and js files
(i.e. css_[md5hash].css) on module updates, etc. Which means cached
dynamic pages end up pointing to non-existent files. An nginx cache
could protect against that problem, but I’m not sure of the best way to
do it.
With nginx proxy_cache you can use “proxy_cache_use_stale” to tell it to
return the last known copy of a cached file on given backend errors.
If you do that for 404 error for css_.css & js_.js, it means that
cached
users will no longer be redirected to non existent css, instead they
will be
loading the css the page was using when it was cached.
Read more here:
Best regards from Montevideo,
Guzmn
On Thu, Oct 14, 2010 at 2:15 PM, brianmercer [email protected]
wrote:
What is the preferred way to cache static files these days? (i.e.
ccs/js)
Recompile with slowfs module
Serve css/js through php backend and use fastcgi_cache
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.