grai-core VS django-dbbackup

Elastic v2 if one is interested in such things: https://github.com/grai-io/grai-core/blob/v0.1.33/LICENSE

I’m not sure if this is precisely what you’re looking for but Grai might serve your needs. The backend data model allows you to push any arbitrary metadata you want / need onto the lineage graph and retrieve it either through the rest or graph API. I’m one of the authors so happy to answer any questions you might have.

We've been looking at building something like this for Grai specifically to support Airflow but haven't yet prioritized it.

We were frustrated because although we had tests in our data warehouse, they only notified us after an outage occurred. What we needed was a way to detect changes during CI/CD, so we could fix things before they impacted production. So we developed Grai, as an open-source data lineage toolkit pre-built integrations for the most common data stores and designed to work with CI tools, like Github Actions.

And finally backups, this part is really important. When I was a beginner, I used to make silly mistakes which would lead me having to reset the entire database and rebuild. With backups you can simply restore back to a working point in time whenever something goes wrong. The django-dbbackup package can do this for you, however, you may run into a few issues which can be fixed. Or you could simply use PostgreSQL database dumps.

I spent the entire day today trying to implement a backup system for my personal Django/Wagtail project using django-dbbackup, however, I ended up making zero progress.

I have a Django/Wagtail project and I'm trying to set up django-dbbackup to backup both my database as well as my media files.

I've just stumbled upon the django-dbbackup package, seems perfect as it backs up the database and media to the cloud. As backups are linked to the deployment using hostnames, it even seamlessly handles restores. I might give that a go using Ofelia to run the backup management command at regular intervals.