Apache is the easiest and most documented route. It is pretty easy to set-up and config so don't let that put you off.
However, I had a situation where I needed a single self-contained install for deployment. On that occasion I used CherryPy3 + WSGI and ran the whole thing as a windows service using the Python Win32 library. It worked out really well. I also had a 'debug' mode where I can run my server from the command line and see all requests etc - again utilising CherryPy3. IMHO, that worked out much better than using Django's test server because it didn't require any extra URL information for serving media. Django's test server isn't going to cut it for deployment and using Apache is simple. Just a few lines of config in httpd.conf and you're done. Avoiding Apache isn't going to make life easier for you. > hi, > > Can I use the django's built in web server in an intranet enviroment > where the maximum users could be not more than 50 users? I am just > asking this for the purpose for easy deployment :). I am very newbie, > and trying to avoid apache > > THanks > james > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
