django-suit VS django-reversion

View on GitHub

Here at Otto srl we (also) develop web applications, and we do that from scratch using the Django framework. We tend to use the Django admin application to provide access to data whenever possible. We used to adopt django-suit as admin application because it really looked nice. The problem is that django-suit was based on bootstrap 2 and even if darklow started developing a v2 based on bootstrap 4, such version never really come to life.

Live Demo: http://djangosuit.com/admin/ Doc: https://django-suit.readthedocs.io/en/develop/ Source: https://github.com/darklow/django-suit

djangosuit.com

django-reversion ([OPTION] For object history and reversion feature, please select right version by your django, see changelog )

I did the initial installation steps and created the initial revisions, but then when I save a model in django shell, the new revision is not created:

I tried django-reversion, django-simple-history, django-audit-log, django-historicalrecords, but I fail to understand how and why I should use each of these packages as some of them seem like an overkill for the requirements. So, after two days of searching and reading through numerous posts about how I should be tracking model changes, I have basically done nothing.

Reversion - looks simple enough to use but not sure how easy it would be to modify it if needed.

Have you checked out django-reversion?

Searching djangopackages.org I was confoosed by django-field-history, "A Django app to track changes to a model field.", and similar apps django-reversion and django-simple-history, I think these are tracking changes to the model itself--the code--inside of admin? Like if you created a Poll which saved results to the database, and later wanted to change one of the Poll questions?