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