0.2.0
Clearer progress. Fewer round trips.
Progress now tells you what is happening and how much is done, instead of showing an internal step number.
Example progress output
Uploading: 250 of 1,095 files — 12.4 MiB of 55.7 MiB total (22%)
Backing up site files: 2,500 of 4,325 files (57%)- Named phases with file/table counts, byte totals, and percentages for the current phase.
- Short deployment summaries by default. Use
--verbosefor every changed/uploaded file and detailed job JSON. - A plain-English explanation of
--dry-run: preview only, with no uploads or replacement of live content. - Up to 20 small files per upload request within a 512 KiB payload limit.
- Up to 100 files per backup/apply/restore-prune request, still bounded by a two-second processing budget.
- Batch uploads retain manifest validation, device ownership, checksums, and safe retry behavior.
Update both parts
The new CLI works with the older connector, but uses single-file uploads and phase-only progress. Update the WordPress connector as well for batching and detailed counts. Rivet does not replace its installed connector during a normal push.
A deterministic test sends 45 small files in three requests instead of 45. Real elapsed time still depends on your network, hosting, file sizes, and database.
Download 0.2.00.1.0
The first public release.
Rivet’s CLI and WordPress connector, created by Craig Gomes and released under the MIT license.
- One-time browser authorization, revocable devices, and multiple saved sites.
- LocalWP detection and Studio SQLite-to-MySQL export support.
- Checksummed file deployment and explicit database table replacement.
- Private timestamped snapshots, restore, resumable server jobs, and cancellation before live changes.
- Bounded retries for safe-to-repeat network requests.
Rivet is still an early release. Read the recovery and compatibility boundaries before deploying to an important site.