Re: Future of serving static content with pylons

2007-07-10 Thread voltron
Thank you Mike and Jose for your answers. @ Mike Where was the 'static' follder situated on your file system? Is it on another drive? My Apache server is on drive C:and all my pylons projects live on D:. Actually I have had that to work well for templates, I create alternate directories for

Re: Future of serving static content with pylons

2007-07-10 Thread Mike Orr
On 7/10/07, voltron [EMAIL PROTECTED] wrote: Thank you Mike and Jose for your answers. @ Mike Where was the 'static' follder situated on your file system? Is it on another drive? It's inside the Pylons project so it's version controlled. And I haven't used Pylons on Windows. The fact

Re: Future of serving static content with pylons

2007-07-10 Thread voltron
According to the docs, os.path.join does throw the drive letters away: http://docs.python.org/lib/module-os.path.html I still think that it would be cool if there was a platform independent way in Pylons for doing this. Another thing, it would also be nice if one could use several static paths

Re: Future of serving static content with pylons

2007-07-10 Thread Philip Jenvey
On Jul 10, 2007, at 11:17 AM, voltron wrote: According to the docs, os.path.join does throw the drive letters away: http://docs.python.org/lib/module-os.path.html I still think that it would be cool if there was a platform independent way in Pylons for doing this. Another thing, it would

Re: Future of serving static content with pylons

2007-07-10 Thread voltron
Actually, the entire app is located on drive D, it is served behind behind an Apache proxy server located on c:. I was looking for a way to ensure that I could configure the path of the static content, for example, images, flash files, javascript files e.t.c. This helps a lot when I´m developing

Re: Future of serving static content with pylons

2007-07-10 Thread Mike Orr
On 7/10/07, Philip Jenvey [EMAIL PROTECTED] wrote: On Jul 10, 2007, at 11:17 AM, voltron wrote: According to the docs, os.path.join does throw the drive letters away: http://docs.python.org/lib/module-os.path.html I still think that it would be cool if there was a platform

Re: Future of serving static content with pylons

2007-07-10 Thread voltron
Hmm, that means I would not need to exclude the stic file folders in my Apache configuration. How should I go about this? I have not found the place where the templates read the folders for static content. Thanks On Jul 10, 9:53 pm, Mike Orr [EMAIL PROTECTED] wrote: On 7/10/07, Philip Jenvey

Re: Future of serving static content with pylons SOLVED

2007-07-10 Thread voltron
I read up the Apache docs, the final headache was caused because of a missing trailing slash at the end of the proxy declarations For those in the same situation, here is my config ( only for windows) VirtualHost * ServerName localhost UseCanonicalName Off DocumentRoot

Re: Future of serving static content with pylons SOLVED

2007-07-10 Thread Jose Galvez
all those slashes will get you every time. I'm glad you got it working jose voltron wrote: I read up the Apache docs, the final headache was caused because of a missing trailing slash at the end of the proxy declarations For those in the same situation, here is my config ( only for

Future of serving static content with pylons

2007-07-09 Thread voltron
I have hit the problem again of serving static content from a directory of my choice. I am serving a Pylons app through an Apache reverse proxy server, on Linux, this works, I set apache to proxy the whole root path. On windows, this just does not work. Would there be a way to set the path

Re: Future of serving static content with pylons

2007-07-09 Thread Mike Orr
On 7/9/07, voltron [EMAIL PROTECTED] wrote: I have hit the problem again of serving static content from a directory of my choice. I am serving a Pylons app through an Apache reverse proxy server, on Linux, this works, I set apache to proxy the whole root path. On windows, this just does

Re: Future of serving static content with pylons

2007-07-09 Thread voltron
Why doesn't it work on Windows? I´m not sure, exactly why, but even when I do this in my Apache config: DocumentRoot / ProxyRequests Off ProxyPass /css ! ProxyPass /flash ! ProxyPass /img ! ProxyPass /scripts ! ProxyPass /games !

Re: Future of serving static content with pylons

2007-07-09 Thread voltron
I noticed this in enviroment.py: root_path = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) paths = {'root_path': root_path, 'controllers': os.path.join(root_path, 'controllers'), 'templates': [os.path.join(root_path, path) for path in \

Re: Future of serving static content with pylons

2007-07-09 Thread Jose Galvez
Hmm I develop with apache on windows. I've not tried your problem yet, but I'll take a look at it Jose voltron wrote: Same result Mike, moving the last two lines above the excludes doe not work, static content is not used by the templates. maybe Apache is doing a DNS lookup on

Re: Future of serving static content with pylons

2007-07-09 Thread Jose Galvez
Dear Voltron, I just tested the whole proxypass thing on my windows box and it works as expected. Looking at your apache confg code below the only thing I see is that DocumentRoot is set incorrectly, if that is really how you have it set that may be the problem. I believe it needs to be set to

Re: Serving static content

2007-05-01 Thread Cliff Wells
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

Re: Serving static content

2007-04-30 Thread Cliff Wells
in /css and /image folders respectively. For production, one would use a Web server like Apache or Cherokee, and since they are the best at what they do, serving static content fast, it would make sense that all static cont be served from them. I have a mild suspicion this is what everyone does

Re: Serving static content

2007-04-30 Thread voltron
like Apache or Cherokee, and since they are the best at what they do, serving static content fast, it would make sense that all static cont be served from them. I have a mild suspicion this is what everyone does. Is there some preferred basic general setup that can be used? I usually