v0.9.2: Supporting Django < 1.10 Middleware

Middleware included in v0.9 didn't work in Django versions 1.8, or 1.9, as noted in issue #16. This has been fixed, and it now works like a charm.

v0.9: Thread-safe

This new release fixes something and adds something.

• Make the app thread safe: If your project has many concurrent Django users logged in and working on the database, you may or may not have seen some mistaken username logs. This has been fixed by making the app thread safe, as explained in issue #6.

• Log only the models that you need to log: a new setting has been added to allow you to log only the models you are interested in. If it is not set, by default django-easy-audit will log every model in the project. Check issue #5 and the settings documentation.

Really happy to see more and more people are using django-easy-audit for their projects!

Kudos!

v0.8: Project Settings

This version of django-easy-audit includes a few nice changes that allow users to control its behaviour. Now it is possible to tell the app not to log certain models' CRUD events, among other things. Head over to the README file to read about the new settings options.

v0.7: Django 1.10 support

Django 1.10 introduced some changes to middleware which made django-easy-audit 0.6 not work properly. Code has been updated to support Django 1.10.

v0.6: Hello, World.

django-easy-audit v0.6

• Logs everytime a user creates, updates or deletes a model registry.
• Logs everytime a user logs in, logs out, or fails to log in.
• Keeps logs in two models: CRUDEvent and LoginEvent.
• Logs can be queried from Django Admin app.
• Supports Python 3.

To-Do

• Admin columns should display more meaningful information and links (for example, a link to the original object in the admin).
• Add admin filters.