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 location as > > > the request never reaches Pylons. > > > > How do you do that during development? Do you hardcode /public/ paths > > for static resources everywhere? > > Actually, I never use webhelpers. I generally use hardcoded paths in my > template and map them in the webserver, but don't see what the issue > would be when using webhelpers. I don't see the whole process as being > very complicated (nor any need to make it complicated).
Well, it can be complicated, for example, you are developing with paster in the url localhost:5000/ But, in production, your web is served under http://mydomain.com/cool/things/... 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. Greetings. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
