getmyenv 0.11.0 → 0.11.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -2
- package/dist/commands/backup.js +2 -2
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -34,8 +34,19 @@ Prompts and status lines go to stderr, so `export --stdout > .env` stays clean.
|
|
|
34
34
|
|
|
35
35
|
Commit `.getmyenv/project.json` and `.getmyenv/template.json`. `token.json` and `claim.json` stay local and are gitignored. `template.json` lists the variable names, never values. In a fresh clone, `npx getmyenv` can start a new project from it and asks for each value.
|
|
36
36
|
|
|
37
|
+
What the CLI writes. Not every folder has all four:
|
|
38
|
+
|
|
39
|
+
```text
|
|
40
|
+
my-app/
|
|
41
|
+
.getmyenv/
|
|
42
|
+
project.json committed. Project id, name and the folder's default context. Written by setup, guest or sign-in.
|
|
43
|
+
template.json committed. Variable names, never values. Written once the project has a variable name.
|
|
44
|
+
token.json gitignored. The folder token. Written by sign-in or guest. Not used with GETMYENV_TOKEN.
|
|
45
|
+
claim.json gitignored, guest only. Claim code and guest passphrase. Keep it private. Written by guest. Deleted by claim.
|
|
46
|
+
```
|
|
47
|
+
|
|
37
48
|
<!-- cli:help -->
|
|
38
|
-
Output of `npx getmyenv --help` (0.11.
|
|
49
|
+
Output of `npx getmyenv --help` (0.11.1):
|
|
39
50
|
|
|
40
51
|
```text
|
|
41
52
|
Usage: getmyenv [options] [command]
|
|
@@ -88,7 +99,7 @@ Environment:
|
|
|
88
99
|
|
|
89
100
|
## Vault password
|
|
90
101
|
|
|
91
|
-
Each context has its own key,
|
|
102
|
+
One Vault password per account unlocks your private key on your device. Each context has its own key, and each reader gets their own sealed copy. Forgot the Vault password? Your recovery code sets a new one in the dashboard. For open contexts, after you enter the Vault password in a terminal, the unlocked context keys stay in your OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service) for 8 hours. The password is never stored.
|
|
92
103
|
|
|
93
104
|
- `npx getmyenv lock` removes every entry. `unlink` removes this project's.
|
|
94
105
|
- Server tokens hold their context key and never ask.
|
package/dist/commands/backup.js
CHANGED
|
@@ -33,6 +33,6 @@ export async function backupCommand(opts) {
|
|
|
33
33
|
writePrivateFile(out, serializeBackup(envelope), { overwrite: false });
|
|
34
34
|
console.log(`${pc.green("✓")} Encrypted backup: ${out} (${data.values.length} values, ${data.contexts.length} open contexts)`);
|
|
35
35
|
console.log(pc.dim(data.recoveryWrappedKey
|
|
36
|
-
? "It opens with your
|
|
37
|
-
: "It opens with your
|
|
36
|
+
? "It opens with your Vault password or recovery code as they are now, not with newer ones. Read-only contexts are backed up from the dashboard."
|
|
37
|
+
: "It opens with your Vault password as it is now, not with a newer one. Read-only contexts are backed up from the dashboard."));
|
|
38
38
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "getmyenv",
|
|
3
|
-
"version": "0.11.
|
|
3
|
+
"version": "0.11.1",
|
|
4
4
|
"description": "CLI for getmyenv, an encrypted store for environment variables and secrets. We store ciphertext only.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
},
|
|
35
35
|
"dependencies": {
|
|
36
36
|
"@getmyenv/crypto": "0.5.0",
|
|
37
|
-
"@getmyenv/shared": "0.10.
|
|
37
|
+
"@getmyenv/shared": "0.10.1",
|
|
38
38
|
"@napi-rs/keyring": "^2.1.0",
|
|
39
39
|
"commander": "^15.0.0",
|
|
40
40
|
"dotenv": "^16.4.7",
|