Not necessarily what you're asking, but services like dnsmadeeasy.com
can do automatic DNS failover. Set up static.example.com to point to
your s3 bucket. dnsmadeeasy (or similar) monitors your s3 bucket,
and switches DNS to your backup if it goes down. Your app only ever
has to point to static.example.com
On Tue, Jul 29, 2008 at 4:42 PM, Jean-Philippe
<skateinmars-/tRiwTcEceKoWZ46qVy/FQ...@public.gmane.org> wrote:
Ian M. Evans a écrit :
Jean-Philippe wrote:
However this rewrite system does not seem clean. I think it would be
better to simply use dns and subdomains for your static files, and change
the subdomain used when s3 is down.
I'm not sure I'm totally following this last paragraph.
Do you mean have two cnames, say, s3.example.com and local.example.com and
change the rewrite depending on the check files existence?
Sorry...up in the wee hours with a head cold. :-(
If you use URL rewriting, your requests will have to go trough nginx to be
redirected, which is inefficient.
Just use an assets servers like files.example.com in an s3 instance. Set up
an additional nginx vhost and if s3 goes down you'll just have to modify the
DNS.
12 messages in ru.sysoev.nginxRe: nginx and self-healing S3 static ...
