hi, i know, i know. the webserver that's started with the "manage.py runserver",
is not meant for production usage. but this is my situation: 1. the system will be used by very few people. i assume at most 10 accounts, and at most 3-4 users working with it at the same time. 2. the program will mostly use only the admin-part. it will be used to feed data into the database (the data is displayed by a different program). 3. i have to make this work on a redhat8 system, where i have only apache1.3 (so no apache2+mod_python). so my plan is to have apache proxy the requests into the internal "runserver"-webserver. (so that the media files can be server by the apachec1.3) questions: 1. except that it was not meant for that, are there any fundamental problems with the "runserver"-webserver? 2. any other ideas? maybe try to compile lighttpd, and then try a fastcgi setup? i'd like to keep the config as simple as possible for now. thanks, gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
