A friendly fork of django-maintenancemode that moves the maintenance mode and ignored url patterns from settings.py to database values.
Python HTML
Pull request Compare This branch is 20 commits ahead, 1 commit behind godshall:master.
Latest commit c86a96e Dec 8, 2015 @alsoicode Update README.rst


This project is no longer maintained and has been moved to: https://github.com/alsoicode/django-maintenancemode-2


django-maintenancemode is a middleware that allows you to temporary shutdown your site for maintenance work.

Logged in users having staff credentials can still fully use the site as can users visiting the site from an ip address defined in Django's INTERNAL_IPS.

This fork moves the maintenance mode property and ignored urls out of settings.py and into your database.

django-maintenancemode works the same way as handling 404 or 500 errors in Django work. It adds a handler503 which you can override in your main urls.py or you can add a 503.html to your templates directory.



Sites must have at least one domain to work properly.


  • Download django-maintenancemode from https://github.com/btaylordesign/django-maintenancemode

  • Install using: python setup.py install

  • In your Django settings file add maintenancemode to your MIDDLEWARE_CLASSES. Make sure it comes after Django's AuthenticationMiddleware. Like so:

  • Add maintenancemode to your INSTALLED_APPS.

  • Run manage.py syncdb to create the necessary tables.

  • Adding the middleware and running your site creates the necessary records in the database to endable/disbale maintenance mode and ignored URL patterns.



Maintenance mode will create a database record per site, read from the domains you have in the Sites app. There is a boolean property on each Maintenance model, "is_being_performed" that takes the place of putting the site into "maintnenace mode" from settings.py


Patterns to ignore are registered as an inline model for each maintenance record created when the site is first run. Patterns should begin with a forward slash: /, but can end any way you'd like.

Some observations:

  • If user is logged in and staff member, the maintenance page is not displayed.
  • If user's ip is in INTERNAL_IPS, the maintenance page is not displayed.