I do my development locally on windows xp. When things are the way I want them, I upload the code to a linux based shared server.
Occasionally, even thought the code works locally, it breaks the live site. This would be much less of a problem if I could display a static page describing to the users that the site is temporarily unavailable because of maintenance. I have been trying to work with the shared server interface to redirect requests to a static site during maintenance. Then I started thinking that it might be better to handle this in middleware. If the user accessing the site was me, the request would get processed normally. But if the request came from anyone else they would get redirected to a static page. In order to have this redirect work, it would have to be very early in the event processing, given that things could be pretty messed up. It would be best if this middleware could be run before any db access is needed, before urls.py and even before settings.py get called. In order to minimize the code that runs, I would be willing to switch this function on and off by manually editing the middleware file. So - django gurus- what do you think of this idea? Any things I should be consider while implementing it? How do others handle this situation? Working late at night may not be an option soon as our site might go global soon. Thanks, Chuck --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
