StoreEnv Beta
Documentation

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

CLI reference

storeenv env

Manage environments: list, use, create, rename, protect, rm.

Global flags
zsh
$ cd ~/code/my-app
$ storeenv env ls
  ENVIRONMENT   SOURCE            FILES   KEYS   LATEST
  default       .env              1       4      1dec82a
  production    .env.production   1       2      e5314c9   protected
  template      generated         1       4      none      read-only
$ storeenv env <action> [name] [new-name]

Arguments

<action>list environments, pick one for this folder (use), or create, rename, protect, unprotect or remove one. One of: ls, list, use, create, rename, protect, unprotect, rm.
<name>Environment name.
<new-name>New name (rename).

Flags

--clearWith use: forget the choice for this folder.
--protectedRequire production access (create).

More examples

$ cd ~/code/my-app
$ storeenv env create staging
  Created environment staging. It maps to .env.staging

Good to know

  • env use <name> picks the environment pull and run use in this folder on this machine only; env use --clear forgets it.
  • Protected environments (production by default) need production access on the member as well as a grant.

Related commands

storeenv pullstoreenv runstoreenv push

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.
Previous rollback Next members