What's Changed
The major feature of this release is periodic snapshot-based backups to S3-compatible storage (#14). To learn more, read the snapshots/backups documentation. Beyond snapshots, we introduced a code of conduct and refactored the client / end-to-end tests as each was growing unruly.
- Add code of conduct by @marcua in #310
- Move databases into their own directory, introduce snapshot path (changes storage format, requires migration) by @marcua in #311
- Unsafe mode for SQLite querying by @marcua in #312
- Introduce scheduled periodic snapshot loop with basic vacuum-based backups by @marcua in #316
- Introduce snapshot model, storage manager, and refactor model macros for reuse by @marcua in #317
- Add support for S3
force_path_style; Introduce localstack for testing; remove debugging symbol details in Cargo.toml by @marcua in #358 - Refactor client functionality in the CLI by @marcua in #365
- Reduce default debugging information for development by @marcua in #367
- Refactor end-to-end tests into smaller groupings by @marcua in #372
- List snapshots endpoint, end-to-end tests, standardize end-to-end test setup, introduce localstack on GH Actions by @marcua in #385
- Ability to restore from a snapshot by @marcua in #405
- Identify snapshots by their hashes by @marcua in #417
- Don't upload snapshot if it's already in S3, prune snapshots once list gets too long by @marcua in #418
- Replace gzip wtih zstd for compressing snapshots by @marcua in #424
- Cleanups/refactors of snapshot execution logic by @marcua in #432
- Add mutex to ensure only one snapshot run happens at a time by @marcua in #444
- Snapshots documentation by @marcua in #446
Full Changelog: v0.1.7...v0.1.8
Contributors
marcua