Serving files in production

2013-04-11 Thread Drew Ferguson
Hi The docs recommend serving static data from a second web server rather than the one serving via WSGI How do folks implement this? I can't figure how to serve data for the same domain using 2 web servers. Am I missing something? -- Drew signature.asc Description: PGP signature

Re: Serving files in production

2013-04-11 Thread Avraham Serour
you can create a subdomain (static.yourdomain.com) and serve static using that, configure the second webserver to serve this subdomain On Thu, Apr 11, 2013 at 2:01 PM, Drew Ferguson wrote: > Hi > > The docs recommend serving static data from a second web server rather > than the one serving via

Re: Serving files in production

2013-04-11 Thread Drew Ferguson
On Thu, 11 Apr 2013 14:54:50 +0300 Avraham Serour wrote: > you can create a subdomain (static.yourdomain.com) and serve static using > that, configure the second webserver to serve this subdomain OK, but then all static references must be prefixed with the domain in templates, etc AND life gets

Re: Serving files in production

2013-04-11 Thread Tom Evans
On Thu, Apr 11, 2013 at 1:50 PM, Drew Ferguson wrote: > On Thu, 11 Apr 2013 14:54:50 +0300 > Avraham Serour wrote: > >> you can create a subdomain (static.yourdomain.com) and serve static using >> that, configure the second webserver to serve this subdomain > > OK, but then all static references

Re: Serving files in production

2013-04-11 Thread Drew Ferguson
Thanks guys, everything is much clearer now And there is even a HOW-TO page https://docs.djangoproject.com/en/1.5/howto/static-files/deployment/ that I also missed as well Cool beans this Django malarky :) On Thu, 11 Apr 2013 14:08:29 +0100 Tom Evans wrote: > On Thu, Apr 11, 2013 at 1:50 PM,