Docs / CLI reference / push
storeenv push
Encrypt and upload your env files as a new version.
$ storeenv push [-m <message>] [--file <path>] [--service <name>] [--env <name>] [--force] [--dry-run]
Flags
| -m, --message | Version message, like a commit message. |
| --file <path> | Push one file only. |
| --service <name> | Push all files of one service. |
| --env <name> | Push only this environment. With --file, map that file to a custom environment. |
| --force | Push on top even if the remote has a newer version. History is kept. |
| --dry-run | Show the plan and upload nothing. |
Example
$ storeenv push -m "Added Razorpay keys" SERVICE FILE ENV CHANGES backend backend/.env default +2 ~1 backend backend/.env.production production +2 default v 9f2c81a "Added Razorpay keys"
Good to know
- Values are never printed by push.
- Only secrets whose value changed are encrypted again. The rest are carried forward.
Global flags
--project <owner/name>, --env <name>, --json, --yes, --no-color, --verbose, --api <url>