@runfile/cli 0.15.0 → 0.16.0

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.
@@ -146,7 +146,7 @@ AES-256-GCM secrets you can commit to git. Auto-decrypted at runtime, never writ
146
146
  tool, no wrapper.
147
147
 
148
148
  ```bash
149
- $ run :env init -p .env.production
149
+ $ run :env init .env.production
150
150
  $ run :env set .env.production DB_PASS "s3cr3t" # auto-encrypted
151
151
  $ run :env set .env.production DB_PASS # omit value → read from stdin (no shell history, no escaping)
152
152
  ```
@@ -160,9 +160,17 @@ You can also use Runfile as a drop-in `dotenvx`/`dotenv` replacement to inject e
160
160
  any command — no Runfile needed:
161
161
 
162
162
  ```bash
163
- $ run :env inject -- node app.js # uses .env by default
164
- $ run :env inject -f .env -f .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
- $ run :env inject -f .env.production -- ./deploy.sh # encrypted values auto-decrypted
163
+ $ run :env inject .env -- node app.js # one file
164
+ $ run :env inject .env .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
+ $ run :env inject .env.production -- ./deploy.sh # encrypted values auto-decrypted
166
+ ```
167
+
168
+ In CI, the file path can be supplied via `RUNFILE_ENV_FILE_TARGET` (set automatically by the
169
+ [setup action's `env-file-source` input](.github/actions/setup/action.yml) for open-source
170
+ repos that keep their encrypted `.env` in a GitHub secret):
171
+
172
+ ```bash
173
+ $ run :env inject -- node app.js # uses $RUNFILE_ENV_FILE_TARGET
166
174
  ```
167
175
 
168
176
  #### Powerful argument substitution
Binary file
@@ -146,7 +146,7 @@ AES-256-GCM secrets you can commit to git. Auto-decrypted at runtime, never writ
146
146
  tool, no wrapper.
147
147
 
148
148
  ```bash
149
- $ run :env init -p .env.production
149
+ $ run :env init .env.production
150
150
  $ run :env set .env.production DB_PASS "s3cr3t" # auto-encrypted
151
151
  $ run :env set .env.production DB_PASS # omit value → read from stdin (no shell history, no escaping)
152
152
  ```
@@ -160,9 +160,17 @@ You can also use Runfile as a drop-in `dotenvx`/`dotenv` replacement to inject e
160
160
  any command — no Runfile needed:
161
161
 
162
162
  ```bash
163
- $ run :env inject -- node app.js # uses .env by default
164
- $ run :env inject -f .env -f .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
- $ run :env inject -f .env.production -- ./deploy.sh # encrypted values auto-decrypted
163
+ $ run :env inject .env -- node app.js # one file
164
+ $ run :env inject .env .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
+ $ run :env inject .env.production -- ./deploy.sh # encrypted values auto-decrypted
166
+ ```
167
+
168
+ In CI, the file path can be supplied via `RUNFILE_ENV_FILE_TARGET` (set automatically by the
169
+ [setup action's `env-file-source` input](.github/actions/setup/action.yml) for open-source
170
+ repos that keep their encrypted `.env` in a GitHub secret):
171
+
172
+ ```bash
173
+ $ run :env inject -- node app.js # uses $RUNFILE_ENV_FILE_TARGET
166
174
  ```
167
175
 
168
176
  #### Powerful argument substitution
Binary file
@@ -146,7 +146,7 @@ AES-256-GCM secrets you can commit to git. Auto-decrypted at runtime, never writ
146
146
  tool, no wrapper.
147
147
 
148
148
  ```bash
149
- $ run :env init -p .env.production
149
+ $ run :env init .env.production
150
150
  $ run :env set .env.production DB_PASS "s3cr3t" # auto-encrypted
151
151
  $ run :env set .env.production DB_PASS # omit value → read from stdin (no shell history, no escaping)
152
152
  ```
@@ -160,9 +160,17 @@ You can also use Runfile as a drop-in `dotenvx`/`dotenv` replacement to inject e
160
160
  any command — no Runfile needed:
161
161
 
162
162
  ```bash
163
- $ run :env inject -- node app.js # uses .env by default
164
- $ run :env inject -f .env -f .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
- $ run :env inject -f .env.production -- ./deploy.sh # encrypted values auto-decrypted
163
+ $ run :env inject .env -- node app.js # one file
164
+ $ run :env inject .env .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
+ $ run :env inject .env.production -- ./deploy.sh # encrypted values auto-decrypted
166
+ ```
167
+
168
+ In CI, the file path can be supplied via `RUNFILE_ENV_FILE_TARGET` (set automatically by the
169
+ [setup action's `env-file-source` input](.github/actions/setup/action.yml) for open-source
170
+ repos that keep their encrypted `.env` in a GitHub secret):
171
+
172
+ ```bash
173
+ $ run :env inject -- node app.js # uses $RUNFILE_ENV_FILE_TARGET
166
174
  ```
167
175
 
168
176
  #### Powerful argument substitution
Binary file
@@ -146,7 +146,7 @@ AES-256-GCM secrets you can commit to git. Auto-decrypted at runtime, never writ
146
146
  tool, no wrapper.
147
147
 
148
148
  ```bash
149
- $ run :env init -p .env.production
149
+ $ run :env init .env.production
150
150
  $ run :env set .env.production DB_PASS "s3cr3t" # auto-encrypted
151
151
  $ run :env set .env.production DB_PASS # omit value → read from stdin (no shell history, no escaping)
152
152
  ```
@@ -160,9 +160,17 @@ You can also use Runfile as a drop-in `dotenvx`/`dotenv` replacement to inject e
160
160
  any command — no Runfile needed:
161
161
 
162
162
  ```bash
163
- $ run :env inject -- node app.js # uses .env by default
164
- $ run :env inject -f .env -f .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
- $ run :env inject -f .env.production -- ./deploy.sh # encrypted values auto-decrypted
163
+ $ run :env inject .env -- node app.js # one file
164
+ $ run :env inject .env .env.local -- pnpm dev # multiple files, last wins; parent env always wins
165
+ $ run :env inject .env.production -- ./deploy.sh # encrypted values auto-decrypted
166
+ ```
167
+
168
+ In CI, the file path can be supplied via `RUNFILE_ENV_FILE_TARGET` (set automatically by the
169
+ [setup action's `env-file-source` input](.github/actions/setup/action.yml) for open-source
170
+ repos that keep their encrypted `.env` in a GitHub secret):
171
+
172
+ ```bash
173
+ $ run :env inject -- node app.js # uses $RUNFILE_ENV_FILE_TARGET
166
174
  ```
167
175
 
168
176
  #### Powerful argument substitution
package/bin/linux-x64/run CHANGED
Binary file
Binary file
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@runfile/cli",
3
- "version": "0.15.0",
3
+ "version": "0.16.0",
4
4
  "description": "Runfile CLI — an easy-to-use, batteries-included task runner",
5
5
  "repository": "https://github.com/Skiley/runfile",
6
6
  "homepage": "https://github.com/Skiley/runfile",