On Tue, Dec 02, 2014 at 11:20:40AM -0500, Martin Owens wrote:
On Mon, 2014-12-01 at 23:42 -0800, Bryce Harrington wrote:
This sounds like excellent news. What does it mean in practice, technically?
We get an account and configure it so that requests pass through their machines on to ours to request files and then cache them. We tell nginx to set a cache timer in the http header so they know how long to keep the files for before refreshing and we set the settings STATIC url to their cdn instead of the local machine.
We require that it be https
And static and media need to be covered. Static files will expire before updates appear, but media files are usually differently named each time.
We might not need the mirror work if fastly are serious in giving us a proper CDN.
Martin,
Thanks for the run down Martin. Shame to see the mirror functionality you did not get put into practice though!
Bryce