On Sat, 2007-02-17 at 23:42 -0800, kbochert wrote: > > > On Feb 17, 11:04 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: [...] > > It will very much vary on a per-host basis. Django code may not be > > responsible for serving all of the URLs for a particular site, for > > example. Somewhere in the web server's configuration (regardless of > > which web server is being used), there will be a setting that says > > "everything under this part of the URL tree gets passed off to that > > Django process over there for processing". Different parts of the URL > > tree may be passed off to different Django instances. So whether Django > > is responsible for serving a response towww.mysite.com/depends on the > > configuration of your site. > > > Do you mean the configuration of my site, or my host's configuration > of the server?
The server: without at least some minimal server configuration (and possibly some intermediate setup on your side as well), your code is never going to be called. > Do I need to talk to my host to find this out, and then have different > url.py > files for development and deployment? > > I.E., how do I design and test a url.py which will work on my host?. Have a look in Django's installation document (and fastcgi setup document) for a couple of examples of how Django can be integrated with a webserver. If you are really confused about this, then trying to install your app in a hosting environment without first testing it on your local machine with your own copy of Apache, etc, is probably going to be a long and frustrating exercise, because you just won't know what to expect or be able to ask the right questions of your hosting provider. The sort of things you would need to know include: are you using mod_python (not particularly common on a cohosting site)? Does your hosting provider support fastcgi so that you can access Django that way? Are they a known Django-friendly hosting provider or do they say "what's Django" (the latter case is much harder for people who are not experienced in setting these things up, because you are going to have to solve almost all problems yourself). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
