Docs / Concepts / Projects, services and environments

Projects, services and environments

How a repository maps to StoreEnv.

The repository is the configuration. Nothing has to be created or mapped by hand.

Git remote	Project. github.com/acme/cakeshop becomes acme/cakeshop.
Folder with an env file	Service. backend/.env belongs to backend. The repository root is called root. Nested folders keep their path, such as apps/web.
.env	The default environment.
.env.<suffix>	An environment named after the suffix. prod becomes production, dev becomes development.
.env.example, .env.sample, .env.template	Not pushed. They are compared against the generated template.

Ignored folders

node_modules, .git, dist, build, .next, coverage, vendor and .venv are skipped. Add more under "ignore" in .storeenv.json.

An optional file you can commit. It never holds secrets.

{
  "ignore": ["fixtures"],
  "environments": { "backend/.env.clienta": "client-a" }
}