Bing wrote:
You should use mod_python and apache. If that is too much trouble (probably is based on how your setup sounds), use fastcgi. Don't use the development server for production.Now if I want to deploy the website so that other people can visit it under my homepage space, http://name.of.some.site/~user/ what should I do?
Mod_python will most certainly involve the system admin-- especially since when the code changes on disk, apache must be reloaded.I am looking at the http://www.djangoproject.com/documentation/modpython/ and am wondering if something can be done without bugging my system admin.
The best way to go about this would be to either 1) continuously bug your system admin for setup/restarts as needed, or 2) bug your system admin once, and have him set up fastcgi for you. You can restart the python process as needed in that situation. It makes for a friendlier way to have django run in a shared environment.Is it possible that I can still use the existing default apache service without creating a new one on a different port?
http://www.djangoproject.com/documentation/fastcgi/ Jeff Anderson
signature.asc
Description: OpenPGP digital signature
