On Dec 2, 4:46 pm, walterbyrd <[EMAIL PROTECTED]> wrote: > All the python frameworks seem to do this: one web-server for > development, another for production. There may be a good reason for > this, but I don't see it. > > If you are doing internet development, then you certainly have a > network. So why not develop on one box, and then move the files to > another? > > For example, this is what I do with php: I mirror my web-site on my > development box. When the files on my development box work the way I > want, I just ftp those files to the web-site. I find this method much > more simple, fast, and robust, than trying to juggle two web-servers > on the same box. > > Also, why is it that with Django I have to restart the web-server, or > touch all files, any time I make any change?
Where do you think it says you have to run two webservers on the same box for development and production? There's certainly no reason to do this unless you want to. Really, your development machine should be completely separate from your production machine. -- DR. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
