Re: Best practice for non-root base URL setup?

John Shaffer wrote: >On 8/18/07, Przemyslaw Wegrzyn <[EMAIL PROTECTED]> wrote: > > >>However Django 0.96 doesn't support named URL patters yet, so I can't >>use {% url %} tag. >> >> > >Even in 0.96, you can use a view as the argument to the url tag. Where >we use "{% url satchmo_cart %}",

Re: Best practice for non-root base URL setup?

On 8/18/07, Przemyslaw Wegrzyn <[EMAIL PROTECTED]> wrote: > However Django 0.96 doesn't support named URL patters yet, so I can't > use {% url %} tag. Even in 0.96, you can use a view as the argument to the url tag. Where we use "{% url satchmo_cart %}", in 0.96 we would have to use "{% url

Re: Best practice for non-root base URL setup?

Chris Moffitt wrote: > We've developed a similar sort of capability for Satchmo. You can > browse the source here- > http://www.satchmoproject.com/trac/browser/satchmo/trunk/satchmo > Seems I've done more or less the same in my

Re: Best practice for non-root base URL setup?

We've developed a similar sort of capability for Satchmo. You can browse the source here- http://www.satchmoproject.com/trac/browser/satchmo/trunk/satchmo -Chris --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Best practice for non-root base URL setup?

Hi! I'd like my customer to be able to deploy my Django application at http://host/some/custom/path/. Deployment is going to use Apache, not yet decided between mod_python and (more likely) FastCGI. One option I see is to use a configurable prefix for all regexp's in top-level url.py, then use