@psg2/env-sync 1.1.0 → 1.1.2
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 +10 -3
- package/dist/cli.js +120 -7066
- package/package.json +18 -11
package/README.md
CHANGED
|
@@ -7,7 +7,13 @@ Define your env vars and secrets in `env-sync.yaml`, then sync them to local `.e
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
|
-
|
|
10
|
+
pnpm add -g @psg2/env-sync
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
Or run it as a one-off without installing:
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
npx @psg2/env-sync
|
|
11
17
|
```
|
|
12
18
|
|
|
13
19
|
## Quick Start
|
|
@@ -90,11 +96,11 @@ targets:
|
|
|
90
96
|
type: vercel
|
|
91
97
|
environments: [production] # preview, production, development
|
|
92
98
|
groups: [prod-secrets]
|
|
93
|
-
project: my-app # Optional
|
|
99
|
+
project: my-app # Optional: expected name of the linked project
|
|
94
100
|
redeploy: true # Optional (default: false)
|
|
95
101
|
```
|
|
96
102
|
|
|
97
|
-
**Authentication:** the token is read from `VERCEL_TOKEN` first, then from the Vercel CLI auth store written by `vercel login` (e.g. `~/Library/Application Support/com.vercel.cli/auth.json` on macOS, `~/.local/share/com.vercel.cli/auth.json` on Linux, `%APPDATA%/com.vercel.cli/auth.json` on Windows). The project and team ids come from `.vercel/project.json`, created by `vercel link` (or written by hand with `projectId` and `orgId`). The `vercel` CLI itself is optional at runtime — it's only needed once, to produce the token and the linked project file.
|
|
103
|
+
**Authentication:** the token is read from `VERCEL_TOKEN` first, then from the Vercel CLI auth store written by `vercel login` (e.g. `~/Library/Application Support/com.vercel.cli/auth.json` on macOS, `~/.local/share/com.vercel.cli/auth.json` on Linux, `%APPDATA%/com.vercel.cli/auth.json` on Windows). The project and team ids come from `.vercel/project.json`, created by `vercel link` (or written by hand with `projectId` and `orgId`). The folder that holds `env-sync.yaml` must be linked; `project:` does not look a project up by name, it only warns when the linked project has a different name. The `vercel` CLI itself is optional at runtime — it's only needed once, to produce the token and the linked project file.
|
|
98
104
|
|
|
99
105
|
#### GitHub
|
|
100
106
|
|
|
@@ -128,6 +134,7 @@ Options:
|
|
|
128
134
|
|
|
129
135
|
| Feature | Requires |
|
|
130
136
|
|---------|----------|
|
|
137
|
+
| Runtime | Node 24 or newer |
|
|
131
138
|
| 1Password secrets | [`op` CLI](https://developer.1password.com/docs/cli) + `op signin` |
|
|
132
139
|
| Vercel targets | `VERCEL_TOKEN` env var, or `vercel login` (CLI optional) |
|
|
133
140
|
| GitHub targets | [`gh` CLI](https://cli.github.com) |
|