StoreEnv Beta
Documentation

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

CLI reference

storeenv namespaces

Namespaces: list, view, projects, claim, status.

Global flags
zsh
$ cd ~/code/my-app
$ storeenv namespaces
  NAMESPACE   KIND           YOUR ROLE
  ada         personal       owner
  acme        organization   owner
  You can create projects in your own namespace and in organizations where you are owner or admin.
$ storeenv namespaces [action] [handle]

Arguments

<action>list your namespaces, view one, list its projects, claim a name left over from 0.1, or see a claim's status. One of: list, view, projects, claim, status. Default: list.
<handle>Namespace name.

Other uses

storeenv namespaces view acmeWho owns acme, and whether it is disputed
storeenv namespaces claim acmeClaim a name left over from StoreEnv 0.1

Good to know

  • Your username is your personal namespace. Organizations are the other kind.
  • claim is for names left over from StoreEnv 0.1 that have no owner yet.

Related commands

storeenv orgsstoreenv projectsstoreenv account

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 orgs Next commit