12 messages in ru.sysoev.nginxRe: nginx and self-healing S3 static ...
FromSent OnAttachments
jeff emmingerJul 25, 2008 2:21 pm 
mikeJul 25, 2008 7:33 pm 
Ian M. EvansJul 25, 2008 11:41 pm 
ThomasJul 26, 2008 2:22 am 
Ian M. EvansJul 26, 2008 2:48 am 
Jean-PhilippeJul 26, 2008 3:04 am 
Ian M. EvansJul 26, 2008 3:20 am 
Jean-PhilippeJul 29, 2008 1:41 pm 
jeff emmingerJul 29, 2008 2:05 pm 
Ian M. EvansJul 29, 2008 5:28 pm 
Jonathan VanascoJul 29, 2008 7:19 pm 
mikeJul 29, 2008 7:46 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: nginx and self-healing S3 static hostingActions...
From:Jean-Philippe (skat@public.gmane.org)
Date:Jul 29, 2008 1:41:52 pm
List:ru.sysoev.nginx

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.