You definitely need your Django code to be in a folder that is unavailable from the Internet. It shouldn't be accessed by your visitors or your server app (such as apache). When you run Django in a production environment, it listens on a specific port, and from there it serves the pages. Apache (or nginx, or whatever) must be configured to accept requests to a certain URL or IP address and hand them off to that port. Incidentally, the ability to do this without jumping through hoops depends on your host. Contact their support, and check out this page: http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
Absolute paths are absolute paths. If you can type 'cd pathname' from any directory and have it always work, then that's what you need. Regarding the path to Python on your host: The steps they provide are referring to CGI scripts, which are executed individually when they are called, very similar to PHP scripts. This has nothing to do with Django, which is a full service that will be running. The information about changing the file extension and the .htaccess file are not relevant to setting up Django. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
