Hacker News Reader

It isn't safe to copy a SQLite database because the file might be in the middle of a transaction. You need to use the ".backup" command instead.

This is true, but because most Wordpress sites hardly ever do inserts etc it’s probably not going to be an issue in this scenario.

If that's true, that's a flaw in SQLite. The plug might be pulled at any moment and you can't stop it.

I am incorrect in this regard.

You can use litestream for proper sqlite replication

What are your thoughts on plugin backward compatibility? That could create a lot of issues. (To be clear, I /love/ the idea of sqlite being the default; I just genuinely can't figure out a way around the plugin headache.)

If running WP this way becomes popular, plugins will adapt and advertise themselves as compatible with SQLite.

I assume there is also a need to backup and deployment for web server configuration too?