sefy-cli 0.4.0 → 0.6.0

package/README.md

@@ -151,17 +151,25 @@ 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.
 
-`sefy-plugin-github` ships alongside the CLI and keeps the vault in a git
-repository - point `SEFY_GITHUB_REPO` at one and `sefy sync` does the rest.
-Authentication is whatever git already does on the machine, so no token is
-stored anywhere.
+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
 future  9.0.0     unusable: it speaks protocol 99 and this build speaks 1
-github  0.4.0     pull, push
+github  0.6.0     pull, push
+sftp    0.6.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
@@ -208,8 +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` (and `cargo install sefy-plugin-github` for the
-git transport)
+**cargo** - `cargo install sefy`, plus `cargo install sefy-plugin-github` or
+`sefy-plugin-sftp` for a transport
 
 **npm** - `npm install -g sefy-cli`
 
@@ -237,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, and 0.4.0 put it to work
-without changing it. 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.4.0",
+  "version": "0.6.0",
   "sefy": {
-    "binary": "v0.4.0"
+    "binary": "v0.6.0"
   },
   "description": "An inconspicuous encrypted store for notes, credentials and files",
   "license": "MIT",