On Tue, Nov 24, 2009 at 11:32 PM, Tim Valenta <[email protected]>wrote:
> Yeah, production servers aren't really very friendly to changes. > Languages like PHP are specifically built to circumvent such woes. > You would have to actually bounce apache in order to get the changes > to take. > > This is why the development server is so nice, because when you alter > certain files that it watches, it actually restarts automatically for > you. There's not really going to be a solution for this problem, > since this is inherent to production-class web servers, where PHP and > general CGI is the exception. > > Hope that's not a big problem! > > I still liked to run a production server version of my project, so I > made a local SVN repository which I would commit changes to. I > checked out a copy of the repository to where my production server > wanted to see it, and then put up a clumsy cron job would > automatically update the production machine's repository each day, and > bounce Apache for me. > > That's about as close as it'll get, I think :P > > You don't give details on what your production environment is so I don't know if you can get closer there, but with mod_wsgi you can get closer. With mod_wsgi in daemon mode just touching the wsgi script file will result in a reload on the next request. You can even set things up so that it reloads automatically on source code changes. Graham Dumpleton sets outs all the details in a blog entry here: http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django.html Karen -- 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?hl=en.
