Great, thanks Cliff. This means I would have to fire up the Pylons
server first? I thought this was just for testing and not really
production usable?
Best
On May 1, 11:43 pm, Cliff Wells <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-04-30 at 10:34 -0700, voltron wrote:
> > Thanks for your answers Cliff. I took a look at Nginx, it looks very
> > interesting, would you care to post an example of your Nginx config
> > file?
>
> Here's a pretty basic setup that proxies to a Pylons backend and serves
> static content from a particular directory:
>
> # server section from nginx.conf
> server {
> listen 123.123.123.123:80;
> server_name www.example.comexample.com;
> access_log /var/log/nginx/example.com-access.log main;
>
> location / {
> proxy_pass http://127.0.0.1:8080;# proxy to pylons app
> include /etc/nginx/proxy.conf; # see below
> }
>
> # static content
> location ~ ^/(images|javascript|css|flash|yui|yui-ext|downloads)/ {
> root /var/www/public_html;
> expires 30d;
> }
> location = /favicon.ico {
> root /var/www/public_html/images;
> }
>
> }
>
> # proxy.conf - common to lots of vhosts
> proxy_set_header Host $host;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> client_max_body_size 10m;
> client_body_buffer_size 128k;
> proxy_connect_timeout 90;
> proxy_send_timeout 90;
> proxy_read_timeout 90;
> proxy_buffer_size 4k;
> proxy_buffers 4 32k;
> proxy_busy_buffers_size 64k;
> proxy_temp_file_write_size 64k;
>
> There's other examples on the Nginx wiki.
>
> Regards,
> Cliff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
