v0.0.11

Full Changelog: v0.0.10...v0.0.11

v0.0.10

What's Changed

• v0.0.10 by @pnwmatt in #36

Full Changelog: v0.0.9...v0.0.10

v0.0.9

What's Changed

• v0.0.8 adds Musl for alpine linux by @pnwmatt in #33
• v0.0.9 - enable ping/pong keep alive for pull subscribe by @pnwmatt in #35

Full Changelog: v0.0.8...v0.0.9

v0.0.8

This version adds support for Alpine Linux (using musl instead of glibc)

Full Changelog: v0.0.7...v0.0.8

v0.0.7

What's Changed

• V0.0.6 by @pnwmatt in #27
• fix: gh-actions restore push main build by @pnwmatt in #28
• fix: suppress ping pong messages in logs by @pnwmatt in #29
• v0.0.7 release by @pnwmatt in #30

Full Changelog: v0.0.6...v0.0.7

v0.0.6

What's Changed

• v0.0.5 release by @pnwmatt in #15
• feat: prompt for key if anon PULL access fails by @pnwmatt in #21
• feat: check integrity before push and after pull by @pnwmatt in #22
• fix: cleanup integrity check code by @pnwmatt in #23
• Configure Dependabot for Go modules in client directory by @pnwmatt in #24
• v0.0.6 by @pnwmatt in #20
• Bump github.com/spf13/cobra from 1.8.0 to 1.10.1 in /client by @dependabot[bot] in #25
• feat: Push subscription and conflict detection. by @pnwmatt in #17

New Contributors

• @dependabot[bot] made their first contribution in #25

Full Changelog: v0.0.5...v0.0.6

v0.0.5

What's Changed

• feat: improve client error reporting from server by @pnwmatt in #19
• feat: send wsID and clientVersion with client requests by @pnwmatt in #16

Full Changelog: v0.0.4...v0.0.5

v0.0.4

Full Changelog: v0.0.1...v0.0.4

Features:

• PUSH and PULL rsync of sqlite3 database files to a remote SQLRsync server (defaults to sqlrsync.com)
• Creates a -sqlrsync file file neighboring the replicated database which can be shared to PULL down the database elsewhere.
• Stores the PUSH key in ~/.config/sqlrsync/ to allow unattended re-PUSHing of the database (great for a cron job)
• LOCAL Sync (when sqlrsync is provided 2 arguments, both local file paths) allows for a local-only (no server/network use) rsyncing of a running write-node SQLite database to a running read-only SQLite database with no readlocks.
• The same mechanism works for PUSH and PULL: the ORIGIN can be a running write-node and the REPLICA can be a running read-only node. It's pretty magical.

In PUSH, PULL, or LOCAL mode:

• Use --dry to dry-run the command and see what mode it will trigger, and an explanation of what it will do

When PUSHing:

• On initial upload you can use the --public or --unlisted flag to allow others to view the webpage for your database, and optionally download any version of it.
• Optionally include a commit message (--message or -m) to keep track of your changes

When PULLing:

• You can append an @ sign and a version reference to download old versions of the database. For example:

sqlrsync oregon/elections.db           # Pulls down the latest version
sqlrsync oregon/elections.db@1         # Pulls down the first version
sqlrsync oregon/elections.db@latest-2  # Goes backwards 2 versions from the latest