docs VS simonwillisonblog-backup

here's the official guide/documentation: https://docs.libretro.com/

We'll deal with it. Looks like it's just the web host, so not that big of a deal. docs.libretro.com and buildbot.libretro.com should still be fine.

I just PRed a blurb that outlines that process based on your comment. Does this look right to you? https://github.com/libretro/docs/pull/840

So, what have you tried for the cheats? Did you make sure the core you're using is compatible with RetroArch's cheats (you can find this information on the cores' pages at docs.libretro.com)?

Sure. You can send PRs to the docs repo https://github.com/libretro/docs/

A log would tell us more, but did you do any of the required setup for those cores? They need BIOS images to function. See the cores' pages on docs.libretro.com for more details.

Emulation Wiki and Libretro docs.

So starting in August 2017, there was a repository called (https://github.com/libretro/docs/) that I contributed frequently to.

> 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