Documentation

Install the CLI, learn the model and look up every command.

CLI reference

storeenv watch

Push automatically when an env file changes.

Global flags
zsh
$ cd ~/code/my-app
$ storeenv watch
Watching env files in ada/my-app. Ctrl+C to stop.
Project ada/my-app (no Git)
Scanning 2 env files (ignored: node_modules, .git, dist, .next)
SERVICE FILE ENV CHANGES
root .env default +1
root .env.production production no changes
Encrypting 1 secret locally and uploading... done
default v 1dec82a "Auto push from watch"
Keys wrapped for 1 member. Template updated. View: storeenv open
Next: run storeenv pull on another machine
Stopped watching.
$ storeenv watch

Flags

--interval <n>Seconds between checks. Default: 2.

Stopped with Ctrl+C after one change.

Good to know

  • Pushes when an env file changes, with the message "Auto push from watch". It never forces: on a conflict it prints the error and keeps watching, so pull and it pushes on the next change.

Global flags

--project <value>Project as <namespace/name> or its id (default: .storeenv.json, then this repository's remotes).
--env <value>Environment name.
--jsonMachine readable output.
--yes, -ySkip confirmations.
--colorColoured output (--no-color to turn off). Default: true.
--verboseShow debug details.
--api <value>API base URL of a self-hosted StoreEnv.
--trust-writer <value>Trust a writer for this run: @login=SE:XXXX-XXXX-XXXX.
--allow-unsignedpull and diff: use values that aren't signed by a trusted writer, after you confirm on a terminal (or with STOREENV_ALLOW_UNSIGNED=1). Never applies to run or copy.