feat: history log setup

alejandrosame commented 11 months ago

The history log is implemented with the package 'django-pghistory', which uses pg triggers.

The summary of changes is as follows:

Changed DATABASE_URL to signal the dependency on postgresql. Migrations won't work anymore with sqlite.
Added python packages 'django-pghistory' and 'django-pgtrigger' (a dependency of the former inside django app).
A basic NixpkgsIssue snapshot model, tracking cve, derivations and statusfields.

This constitutes the building blocks for all activity log we want to register.

alejandrosame commented 10 months ago

There are migration errors in main that prevent me from finishing a proper rebase. They should be fixed there first so I can rebase again.

alejandrosame commented 10 months ago

This PR is in a working state again.

After much fiddling with the default admin views of pghistory, I don't find them very usable. Taking this as starting point, I'll now create an Activity Log app to put there usable custom views of the different tables tracking the changes we want to summarise.

Nix-Security-WG / nix-security-tracker

feat: history log setup #101