Skip to main content

Unified, persistent and dynamic user messages/notifications for Django

Project description

Monitio for Django

Monitio allows you to have messages (aka notifications), that:

* can be persisted (stored in the database and read later),
* which dynamically show on the web UI when added,
* and can be optionally sent via e-mail to your end-user.

Monitio is built upon:

* [django-sse](
* which uses [django-redis](
* ... and [Redis database](
* [Yaffle's EventSource.js]( for cross-browser Server-Sent Events compatibility
* [django-cors-headers]( for the same thing
* [django-transaction-signals](
* [jQuery]( and [jQueryUI](

With such sophisticated setup, using packages from many individuals, the demo
application is currently properly running on MSIE 10, Opera 12, FFox 16 and
Safari 5.1.7 on Windows. Also, monitio has been tested in production environment
with nginx + gunicorn, which also has been found to work properly.


A Django app for unified, persistent and live user messages/notifications, built on top of Django's [messages framework]( (`django.contrib.messages`).

Monitio is a messages storage backend that provides support for messages that are supposed to be persistent, that is, they outlast a browser session and will be stored in the database. These messages can be displayed as you will to the user, you can let the user mark them as read, remove them or even reply them. For some of these actions there are views you can import in your project

* Support persistent and nonpersistent messages for authenticated users. Persistent messages are stored in the database.
* For anonymous users, messages are stored using the cookie/session-based approach. There is no support for persistent messages for anonymous users.
* There is a unified API for displaying messages to both types of users, that is, you can use the same code you'd be using with Django's messaging framework in order to add and display messages, but there is additional functionality available if the user is authenticated.


This document assumes that you are familiar with Python and Django.

1. Clone this git repository (no PyPI package for this fork). master branch is the lastest stable branch:

$ git clone git://

2. Make sure `monitio` is in your `PYTHONPATH`.
3. Add `monitio` & company to your `INSTALLED_APPS` setting.


4. Make sure Django's `MessageMiddleware` is in your `MIDDLEWARE_CLASSES` setting (which is the case by default), also enable `CorsMiddleware` there. Add `LocaleMiddleware` if you want to use translations:


5. Add the CONTEXT_PROCESSOR for messages and static URL:


6. Add the `monitio` URLs to your URL conf. For instance, in order to make messages available under ``, add the following line to ``.

urlpatterns = patterns('',
(r'^messages/', include('monitio.urls', namespace='monitio')),

7. In your settings, set the message [storage backend]( to ``:


8. In your settings, add a reasonable default, which will prevent from showing read messages to the users:


9. Setup `django-sse` and `corsheaders`:

'location': '',
'db': 0,


10. Set up the database tables using

$ syncdb

11. If you want to use the bundled templates, add the `templates` directory to your `TEMPLATE_DIRS` setting:


12. Setup a production server - for [nginx]( + [gunicorn](, please use configuration below:

location ~ ^/messages {
proxy_pass http://your-gunicorn-address.../
proxy_buffering off;
proxy_cache off;
proxy_set_header Host $host;

proxy_set_header Connection '';
proxy_http_version 1.1;
chunked_transfer_encoding off;

And, for [gunicorn](, make sure you install [gevent]( and run [gunicorn]( with parameter `-k gevent`

Using messages in views and templates

### Message levels ###

Django's messages framework provides a number of [message levels]( for various purposes such as success messages, warnings etc.

import monitio
# persistent message levels:

This app provides constants with the same names, the difference being that messages with these levels are going to be persistent:

from django.contrib import messages
# temporary message levels:

**Note**: Let's stress the importance of this. If you use `monitio` constants the message will be stored in the database and kept there till somebody explicitly deletes it. If you use `contrib.messages` constants, you get the same behavior as if you were using a non persistent storage, messages are stored in the database ensuring reception but they are removed right after being accessed.

### Adding a message ###

Since the app is implemented as a [storage backend]( for Django's [messages framework](, you can still use the regular Django API to add a message:

from django.contrib import messages
messages.add_message(request, messages.INFO, 'Hello world.')

This is compatible and equivalent to using the API provided by `monitio`:

import monitio
from django.contrib import messages
monitio.add_message(request, messages.INFO, 'Hello world.')

In order to add a persistent message (one that is stored permanently in the Database), use `monitio` levels listed above:

messages.add_message(request, monitio.WARNING, 'This message is stored in monitio table till removed.')

or the equivalent:

monitio.add_message(request, monitio.WARNING, 'This message is stored in monitio table till removed')

Note that this is only possible for logged-in users, so you are probably going to have make sure that the current user is not anonymous using `request.user.is_authenticated()`. Adding a persistent message for anonymous users raises a `NotImplementedError`.

### Extended API ###

Persistent Messages has an extended API that will let you do some extra nice things. This is the prototype of `add_message` in contrib messages:

def add_message(request, level, message, extra_tags='', fail_silently=False):

This is the prototype of `add_message` in Persistent Messages.

def add_message(request, level, message, extra_tags='', fail_silently=False, subject='', user=None, email=False, from_user=None, expires=None, close_timeout=None):

#### Subject and email notifications ####

Using `monitio.add_message`, you can also add a subject line to the message. You can also set if you want an email notification to be sent. The following message will be stored as a message in the database and also sent to the email address associated with the current user:

monitio.add_message(request, monitio.INFO, 'Message body', subject='Please read me', email=True)

**Note!** Email notifications at the moment are too simple, I don't recommend using them, I'm not.

#### Send messages to different users ####

You can also pass this function a `User` object if the message is supposed to be sent to a user other than the one who is currently authenticated. User Sally will see this message the next time she logs in:

from django.contrib.auth.models import User
sally = User.objects.get(username='Sally')
monitio.add_message(request, monitio.SUCCESS, 'Hi Sally, here is a message to you.', subject='Success message', user=sally)

You can also set a `from_user`, which lets you use Persistent Messages as messaging system between users.

#### You can make messages expire ####

You need to pass a date and time to `expires` argument. Once the message has expired, it will not be included in the returned QuerySet. At the moment there is no view or method to clear expired messages from database.

### Displaying messages ###

To add monitio to your template:

* add to `<head>` section:
{% include "monitio/header.html" %}

This will include `yaffle.js`, `monitio.js` monitio translations and themes.

* in the `<body>` section, place the message placeholder anywhere you like:

<div id="monitioMessages"></div>

* ... and initialize monitio, optionally passing theme parameter:
$(document).ready(function () {
"url": '{% url "monitio:persistent-messages-sse" user.username %}',
"theme": "foundation" // remove for jqueryui theme
* don't forget to add links to `jquery`, `jqueryui` and optionally to `foundation 5`

* if any problems, check `foundation_index.html` in the `test_app/templates` directory, as it is much simpler than original one.

### Creating notifications from background tasks (eg. Celery) ###

To create a notofication from a long-running, background process, use

def create_message(to_user, level, message, from_user=None, extra_tags='',
subject='', expires=None, close_timeout=None, sse=True,

This function will call PersistentStorage.add method for you.

### Storage extra methods ###

In Django `request._messages` is set to the default storage you configured in your settings. Persistent Messages storage has some extra methods that Django built-in storages don't have that can be very useful:

* **get_persistent**: Get read and unread persistent messages
* **get_persistent_unread**: Get unread persistent messages
* **get_nonpersistent**: Gets nonpersistent messages
* **count_unread**: Counts persistent and nonpersistent unread messages
* **count_persistent_unread**: Counts persistent unread messages
* **count_nonpersistent**: Counts nonpersistent messages

Let's see some examples of what this means.

#### Display number of unread messages ####

Imagine you've created an inbox for your users using Persistent Messages and you want to show them in the menu how many unread messages they have, if they have them:

<ul id="menu">
<li><a href="">inbox {% if messages.count_persistent_unread > 0 %}({{ messages.count_persistent_unread }}){% endif %}</a></li>

### AUTHORS ###

django-monitio is (C) 2013 [mpasternak](

[philomat]( is the author of original code for
which was then forked by [maurojp](

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution (42.0 kB view hashes)

Uploaded source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page