Molecule
Test your Ansible roles and collections in throwaway containers or VMs.
Continuously stream SQLite changes to S3-compatible storage.
No votes yet. Tried it? Be the first to say.
One vote per person. No account needed.
Litestream runs alongside your app and replicates the SQLite write-ahead log to object storage within seconds, so a single-server SQLite app gets point-in-time restore without a database server.
Nightly cron backups of a .sqlite file, or moving to Postgres just for durability
You run SQLite in production and losing a day of data would hurt.
Streams SQLite's write-ahead log (WAL) to object storage, typically within a second or so of each write.
S3 and S3-compatible storage (Backblaze B2, Cloudflare R2, MinIO), Google Cloud Storage, Azure Blob, SFTP or a local path.
Restore the latest state or a specific timestamp with one command.
Periodic snapshots plus WAL segments, with configurable retention.
litestream replicate -exec "your-app" runs your app as a child process and replicates alongside it.
Works with any SQLite database; your code doesn't know it's there.
SQLite in WAL mode writes changes to a separate log file before checkpointing them into the main database. Litestream holds a read transaction to control checkpointing, copies new WAL frames as they appear, and ships them to your replica destination in small segments, plus periodic full snapshots. Restoring means downloading the latest snapshot and replaying the WAL segments after it.
# /etc/litestream.yml
dbs:
- path: /app/data/app.sqlite
replicas:
- type: s3
bucket: my-backups
path: app.sqlite
endpoint: https://s3.eu-central-1.amazonaws.com
retention: 72hCredentials come from the usual AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.
Restore on boot if the database is missing, then run the app under Litestream:
litestream restore -if-db-not-exists -if-replica-exists /app/data/app.sqlite
exec litestream replicate -exec "node dist/server/entry.mjs"This makes the server effectively disposable: a fresh container rebuilds its database from object storage and carries on.
PRAGMA journal_mode = WAL); Litestream requires it.litestream restore -timestamp 2026-11-01T12:00:00Z ... restores to a point in time.litestream replicate app.db s3://my-bucket/app.db
# restore:
litestream restore -o app.db s3://my-bucket/app.db From the same author's lineage at Fly.io, offering live replicas across nodes with a FUSE file system; more complex.
Simple periodic snapshots, but you lose everything since the last one.
Built-in replication and HA, at the cost of running a database server.
Distributed SQLite with Raft for real high availability.
Other tools that share topics with Litestream.
Test your Ansible roles and collections in throwaway containers or VMs.
Spin up real databases and services in Docker from inside your tests.
A web server and reverse proxy with automatic HTTPS.