On Tue, 2008-06-17 at 19:55 -0700, Shannon -jj Behrens wrote:
On Mon, Jun 16, 2008 at 2:37 PM, Cliff Wells [EMAIL PROTECTED] wrote:
On Mon, 2008-06-16 at 14:26 -0700, Cliff Wells wrote:
On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote:
I am trying to figure out what the best
Previously Cliff Wells wrote:
On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote:
I am trying to figure out what the best practices for dealing with
static resources such as CSS, Javascript and images are. With a
default pylons setup every request goes through two StaticURLParser
On Tue, 2008-06-17 at 10:36 +0200, Wichert Akkerman wrote:
Previously Cliff Wells wrote:
I usually just setup Nginx to handle whatever location my static content
is at. It doesn't matter if Routes is setup to handle that location as
the request never reaches Pylons.
How do you do
El mar, 17-06-2008 a las 04:33 -0700, Cliff Wells escribió:
On Tue, 2008-06-17 at 10:36 +0200, Wichert Akkerman wrote:
Previously Cliff Wells wrote:
I usually just setup Nginx to handle whatever location my static content
is at. It doesn't matter if Routes is setup to handle that
Previously Antonio Beamud Montero wrote:
El mar, 17-06-2008 a las 04:33 -0700, Cliff Wells escribió:
On Tue, 2008-06-17 at 10:36 +0200, Wichert Akkerman wrote:
Previously Cliff Wells wrote:
I usually just setup Nginx to handle whatever location my static content
is at. It
On Tue, 2008-06-17 at 14:23 +0200, Antonio Beamud Montero wrote:
I use the url_for for all static content, and with mod_wsgi all is
transparent (thanks G. Dumpleton :), doesn't matter where you put your
web root.
I have all my static content urls hardcoded, I was not able to figure
out how
On Mon, Jun 16, 2008 at 2:37 PM, Cliff Wells [EMAIL PROTECTED] wrote:
On Mon, 2008-06-16 at 14:26 -0700, Cliff Wells wrote:
On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote:
I am trying to figure out what the best practices for dealing with
static resources such as CSS, Javascript
I am trying to figure out what the best practices for dealing with
static resources such as CSS, Javascript and images are. With a
default pylons setup every request goes through two StaticURLParser
instances and files returned by them do not get any caching headers.
This is very practical for
On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote:
I am trying to figure out what the best practices for dealing with
static resources such as CSS, Javascript and images are. With a
default pylons setup every request goes through two StaticURLParser
instances and files returned by
On Mon, 2008-06-16 at 14:26 -0700, Cliff Wells wrote:
On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote:
I am trying to figure out what the best practices for dealing with
static resources such as CSS, Javascript and images are. With a
default pylons setup every request goes
i do this:
server {
listen 80;
server_name
myapp.com
www.myapp.com
;
access_log /var/log/nginx/myapp/myapp.com-access.log main;
error_log /var/log/nginx/myapp/myapp.com-error.log ;
location ~ ^/(_img|_css|_js) {
include
11 matches
Mail list logo
