Address PR feedback from @benbjohnson: 1. Make socket opt-in (no default path) - Users commonly run multiple Litestream instances - Default socket would cause conflicts between instances - Socket now only enabled when path is explicitly configured 2. Move socket to nested config section - Before: socket, socket-permissions, persist-to-config - After: socket.path, socket.permissions, socket.persist-to-config Changes: - Add SocketConfig struct with path, permissions, persist-to-config - Update Config struct to use nested Socket field - Remove default socket path from DefaultConfig() - Update control commands to require -socket flag - Update replicate.go to check Socket.Path - Update control.go to use Socket.PersistToConfig - Update documentation with new config format Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Litestream

Litestream is a standalone disaster recovery tool for SQLite. It runs as a background process and safely replicates changes incrementally to another file or S3. Litestream only communicates with SQLite through the SQLite API so it will not corrupt your database.
Litestream also provides runtime control commands for dynamically managing
database replication without restarting the daemon. See docs/IPC_CONTROL.md
for details on using start, stop, sync, and status commands.
If you need support or have ideas for improving Litestream, please join the Litestream Slack or visit the GitHub Discussions. Please visit the Litestream web site for installation instructions and documentation.
If you find this project interesting, please consider starring the project on GitHub.
Contributing
We welcome bug reports, fixes, and patches! Please see our Contributing Guide for details on how to contribute.
Acknowledgements
I want to give special thanks to individuals who invest much of their time and energy into the project to help make it better:
- Thanks to Cory LaNou for giving early feedback and testing when Litestream was still pre-release.
- Thanks to Michael Lynch for digging into issues and contributing to the documentation.
- Thanks to Kurt Mackey for feedback and testing.
- Thanks to Sam Weston for figuring out how to run Litestream on Kubernetes and writing up the docs for it.
- Thanks to Rafael & Jungle Boogie for helping to get OpenBSD release builds working.
- Thanks to Simon Gottschlag, Marin,Victor Björklund, Jonathan Beri Yuri, Nathan Probst, Yann Coleu, and Nicholas Grilly for frequent feedback, testing, & support.
Huge thanks to fly.io for their support and for contributing credits for testing and development!