Interesting, i've been looking for something like this to smooth out the rollout of new changes.
Is there any reason why you don't use something like 'assets/bg.sfw?cachifest=v1354729620000203' instead of 'assets/bg_v1354729620000203.swf' for the replacement url? That way you shouldn't need any extra configuration in your web server. On Sunday, April 7, 2013 7:35:15 PM UTC+2, Alexey Kupershtokh wrote: > > https://github.com/AlexeyKupershtokh/cachifest > > понедельник, 8 апреля 2013 г., 0:34:51 UTC+7 пользователь Alexey > Kupershtokh написал: >> >> It seems that I forgot to post an announce for another module I created >> recently. I'll just quote its documentation: >> >> This is a command line tool for watching for directory changes. Each time >> a file is updated in this directory, cachifest assembles an updated >> manifest.json file which has a map of file renames >> >> cachifest is useful for making efficient http caching with following >> features: >> >> 1. All static files have far future expiration without revalidation. >> 2. If a static file changed it should be invalidated by composing a >> new unique url for it. >> 3. Developers and admins don't need to run any maintenance scripts >> after rolling new changes to servers. >> >> -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
