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 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/...
And then you want to scale up even further and have to offload static resources to another machine. You don't want to have to edit all your templates to do that. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
