On Sun, Apr 27, 2008 at 9:33 AM, notfound <[EMAIL PROTECTED]> wrote: > > 2008/4/27 James Bennett <[EMAIL PROTECTED]>: > > > > On Sun, Apr 27, 2008 at 7:17 AM, notfound <[EMAIL PROTECTED]> > wrote: > > > No, that's a hosted server, I don't have access to Apache > > > unfortunately. Is there any other way I could make it reload the > code? > > > > Not really, no. In a production deployment, the code stays resident in > > memory for the life of a server process, and does not (for performance > > reasons) automatically reload any time you change a file. Which means > > that when you make a change, you have to restart the server process. > > If your hosting doesn't let you do this, you probably need a different > > hosting arrangement. > > Ok, thanks for the info. I'll ask them to restart Apache on Monday > then (there's no helpline or anything, another good reason for > changing hosting). > > Meantime however, as I still need to make these updates and I have > only live (well, not quite yet, as it is still not officially live) > site, is there any way of testing the changes I'm doing on it? Or do I > just have to make them, upload to the server, ask hosting company to > restart Apache and keep my fingers crossed that it works?
Just test them on your own machine using the development server. Updating the live server with untested code is, um, risky. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
