getmyenv 0.12.0 → 0.12.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 +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -49,7 +49,7 @@ my-app/
|
|
|
49
49
|
```
|
|
50
50
|
|
|
51
51
|
<!-- cli:help -->
|
|
52
|
-
Output of `npx getmyenv --help` (0.12.
|
|
52
|
+
Output of `npx getmyenv --help` (0.12.1):
|
|
53
53
|
|
|
54
54
|
```text
|
|
55
55
|
Usage: getmyenv [options] [command]
|
|
@@ -111,7 +111,7 @@ One Vault password per account unlocks your private key on your device. Each con
|
|
|
111
111
|
|
|
112
112
|
## CI and servers
|
|
113
113
|
|
|
114
|
-
Create a server token for one context
|
|
114
|
+
Create a server token for one context in Project settings, Tokens. It holds that context's key.
|
|
115
115
|
|
|
116
116
|
```bash
|
|
117
117
|
export GETMYENV_TOKEN=... # server token from the dashboard
|
|
@@ -120,7 +120,7 @@ npx getmyenv run -- node server.js
|
|
|
120
120
|
|
|
121
121
|
Server tokens are read-only. `set` needs the folder token from browser sign-in, or a guest project. `printf %s "$VALUE" | npx getmyenv set API_KEY --stdin` keeps the value out of argv.
|
|
122
122
|
|
|
123
|
-
- `GETMYENV_TOKEN`: a token from
|
|
123
|
+
- `GETMYENV_TOKEN`: a server token from Project settings, Tokens.
|
|
124
124
|
- `GETMYENV_CONFIG_DIR`: machine key and cache (default `~/.config/getmyenv`). Use a persistent volume in containers.
|
|
125
125
|
- `GETMYENV_API_URL`: API origin. https only, http for localhost.
|
|
126
126
|
- `GETMYENV_MACHINE_LABEL`: the machine name shown in approval requests.
|