The big value for me of the dev server is the ease with which I can get debugging information out of it.
Of course, I fully understand that it is not suitable for serving my site - I didn't mean to give the impression that it was. But the cycle of using the dev-server for making something work, then moving everything onto the production server seems like an path that most people would want. Getting info out of my views.py code while I'm hacking something up is pretty tough otherwise. Thanks for clarifying that the 'trigger' word is called the SCRIPT_NAME. I'll look around for something that clarifies how to use SCRIPT_NAME properly - I guess that's really what my whole question was. Any suggestions where to find examples for that? Ross. On Mar 23, 9:03 pm, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: ...snip... > > If the dev server doesn't meet your needs and you need a full webserver, > then do exactly that: use a full-powered web server. Normally, though, > this shouldn't really matter. All the links within your site can be made > to work without caring about the SCRIPT_NAME (e.g. the "url" template > tag adds it when required), so it's good practice to build your site > being able to move it to a different SCRIPT_NAME prefix. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
