sefy-cli 0.3.1 → 0.5.0

package/README.md

@@ -106,9 +106,19 @@ error: 2 items match "ma":
 narrow the text, or use an id
 ```
 
-Two machines, two copies, both edited? Fold one into the other. Where they
-disagree about the same item, sefy keeps both versions rather than letting a
-timestamp decide which password you get to keep:
+Several machines? `sefy sync` carries the vault through a transport and folds
+what comes back into this one:
+
+```
+$ sefy sync
+Master password:
+synced "vault" through github
+merged: 2 added, 0 updated, 14 unchanged
+```
+
+Or fold in a copy you carried across by hand. Either way, where the two disagree
+about the same item, sefy keeps both versions rather than letting a timestamp
+decide which password you get to keep:
 
 ```
 $ sefy merge ~/from-laptop.bak
@@ -141,17 +151,29 @@ named `sefy-plugin-*`, found in sefy's data directory or on `PATH`. sefy knows
 nothing about git, FTP or any cloud drive - it asks a plugin what it can do and
 what happened.
 
+Two transports ship alongside the CLI, and neither stores a credential of its
+own - each authenticates the way the machine already does:
+
+- **github** keeps the vault in a git repository. Point `SEFY_GITHUB_REPO` at
+  one; version history comes free with it.
+- **sftp** keeps it on a server you control, over OpenSSH. Point
+  `SEFY_SFTP_DESTINATION` at `you@server:/path`; nothing lands there but the
+  blob.
+
 ```
 $ sefy plugin list
-ftp     0.2.1     push
 future  9.0.0     unusable: it speaks protocol 99 and this build speaks 1
-github  0.1.0     pull, push
+github  0.5.0     pull, push
+sftp    0.5.0     pull, push
 ```
 
+With more than one installed, sefy asks which rather than choosing where your
+vault goes: `sefy sync --transport sftp`, or `SEFY_TRANSPORT=sftp` once.
+
 A transport is handed the **path of the sealed file** and nothing else - no
 master password, no key, no item. What it carries is what anyone would find on
-your disk: a blob it cannot read. That is also why a plugin cannot merge; it
-fetches the other copy to a file, and `sefy merge` folds the two together where
+your disk: a blob it cannot read. That is also why a plugin cannot merge: it
+moves the other copy to a file, and sefy folds the two together itself, where
 both sides can actually be read.
 
 Broken plugins are listed with the reason rather than skipped: an omitted line
@@ -194,7 +216,8 @@ curl -fsSL https://raw.githubusercontent.com/lacodda/sefy/main/tools/install.sh
 
 On Windows use the PowerShell line above: `install.sh` carries the macOS and Linux builds only, and run from Git Bash it stops with a pointer back here.
 
-**cargo** - `cargo install sefy`
+**cargo** - `cargo install sefy`, plus `cargo install sefy-plugin-github` or
+`sefy-plugin-sftp` for a transport
 
 **npm** - `npm install -g sefy-cli`
 
@@ -203,7 +226,9 @@ On Windows use the PowerShell line above: `install.sh` carries the macOS and Lin
 `PATH`.
 
 Both installers take the newest release by default; set `SEFY_VERSION` to a tag
-to pin one, and `SEFY_INSTALL_DIR` to choose where the binary lands.
+to pin one, and `SEFY_INSTALL_DIR` to choose where the binary lands. They also
+place any transport the archive carries into sefy's plugins directory, so
+`sefy plugin list` finds it without a second step.
 
 Shell completions: `sefy completions bash` (also `zsh`, `fish`, `powershell`,
 `elvish`).
@@ -220,10 +245,12 @@ The database inside the ciphertext is versioned separately, and it does move:
 from 0.1.x opens, is migrated on the way in, and is still readable by 0.1.x
 afterwards - the file on disk did not change shape.
 
-The **plugin protocol is at version 1** as of 0.3.0. Optional fields may be
-added to the manifest without breaking a plugin that predates them; changing
-what an existing field means would arrive as version 2, with both accepted for a
-time.
+The **plugin protocol is at version 1** as of 0.3.0. 0.4.0 put it to work and
+0.5.0 added a second transport of a different shape without changing a field of
+it, which is the evidence that it was not built around the first one. Optional
+fields may be added to the manifest without breaking a plugin that predates
+them; changing what an existing field means would arrive as version 2, with both
+accepted for a time.
 
 Released versions and what landed in each: [CHANGELOG on the Releases page](https://github.com/lacodda/sefy/releases).
 

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "sefy-cli",
-  "version": "0.3.1",
+  "version": "0.5.0",
   "sefy": {
-    "binary": "v0.3.1"
+    "binary": "v0.5.0"
   },
   "description": "An inconspicuous encrypted store for notes, credentials and files",
   "license": "MIT",