simonwillisonblog-backup VS wayback-machine-downloader

> I’ve been running that for a couple of years in this repo: https://github.com/simonw/simonwillisonblog-backup - which provides a backup of my blog’s PostgreSQL Django database (first converted to SQLite and then dumped out using sqlite-

I'm curious, what is the reason you chose not to use pgdump, but instead opted to convert to to sqlite and then dump the DB using sqlite-diffable?

On a project I'm working on, I'd like to dump our Postgres schema into individual files for each object (i.e., one file for each table, function, stored proc, etc.), but haven't spent enough time to see if pgdump could actually do that. We're just outputting files by object type for now (one tables, function, and stored procs files).

My personal blog runs on Django + PostgreSQL, and I got fed up of not having a version history of changes I made to my content there.

I solved that by setting up a GitHub repo that mirrors the content from my database to flat files a few times a day and commits any changes.

It's worked out really well so far. It wasn't much trouble to setup and it's now been running for nearly three years, capturing 1400+ changes.

I'd absolutely consider using the same technique for a commercial project in the future:

Latest commits are here: https://github.com/simonw/simonwillisonblog-backup/commits/m...

Workflow is https://github.com/simonw/simonwillisonblog-backup/blob/main...

If you really, really need to be able to see a SQL schema representing the current state, a cheap trick is to run an automation on every deploy that snapshots the schema and writes it to a GitHub repository.

I do a version of that for my own (Django-powered) blog here: https://github.com/simonw/simonwillisonblog-backup/blob/main...

My blog is Django and PostgreSQL on Heroku, but last year I decided I wanted a reliable long-term public backup... so I set up a scheduled GitHub Actions workflow to back it up to a git repository.

Bonus feature: since it runs nightly it gives me diffs if changes I make to my content, including edits to old posts.

The backups are in this repo: https://github.com/simonw/simonwillisonblog-backup

I just found this https://github.com/hartator/wayback-machine-downloader

anyone have anything similarly interesting/cool/niche-useful ?

Send ArchiveTeam the link on IRC or here and we can save it to archive.org, then later you can use wayback-machine-downloader to grab it from archive.org.

https://github.com/hartator/wayback-machine-downloader

This is where it gets tricky, you need to download the code from the wayback machine and he was able to do that by following these steps: https://github.com/hartator/wayback-machine-downloader

Not sure if it will work for twitter, but I have used wayback-machine-downloader to batch download stuff.

Adding to archive.org, there is a github repo to fetch website data. You can give a try too. Here is the repo link

Edit: Good news! I found a solution that saved me. I was able to download the full website (including images, JS, and CSS files) using this tool: https://github.com/hartator/wayback-machine-downloader

Edit: Thank you to everyone who suggested the Wayback Machine Downloader! It saved the day and allowed me to download the full website, including images, JS, and CSS files.

I've used https://github.com/hartator/wayback-machine-downloader but it sometimes messes up CSS badly