the dev server is not robust. it cannot be used in a production environment (to serve your site that is) but it can be used for development. after you finish your development, you deploy your application to be served by apache or some other real server. but there is no need to torture your self restarting apache after every single change :)
konstantin On Sep 16, 8:17 am, Cequiel <[EMAIL PROTECTED]> wrote: > Hi akonsu. > > I wasn't sure about the django dev server. I thought that the django > dev server was created only to follow the tutorials and for making > your first silly applications. But is the django dev server a complete > and a robust web server? In this case I'll use this server instead. > > Thanks. > > On 16 sep, 06:11, akonsu <[EMAIL PROTECTED]> wrote: > > > hello, > > > would django dev server be a useful alternative for you? it picks up > > most changes without a restart. > > > konstantin > > > On Sep 15, 11:27 pm, Cequiel <[EMAIL PROTECTED]> wrote: > > > > Hi all. > > > > I installed Django with Apache in my Windows. It was a little > > > complicated but finally it is working fine. But I have another litle > > > problem. When I change part of my code I need to restart the apache > > > server to see the changes in the browser and I lost at least 10 > > > seconds in this operation (and 10 seconds multiplied by 1000 times are > > > 10000 seconds, that is 2'7 hours approximately at day :¬) ) > > > > An my question is if is there a way to avoid restarting the apache > > > server every time I make a modification? > > > > Thanks in advantage and sorry for my English. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---