Emily CLI Documentation

Emily Environments

In Emily, projects are developed and deployed by means of three core concepts: environments, configuration, and deployments. In Emily, environments define the environment variables exposed to a project when it's running, whether it's running locally during development, or an a server in production.

When building a project, a default environment called dev is created. The contents of the environment can be seen at <project root>/environments/dev.

Inside <project root>/environments/dev there is a single file called .emily.env. This file specifies basic environment variables needed to run the project.

When running or deploying projects, Emily will gather all *.env files, merge their contents and write them to <project root>/configurations/<configuration>/.env. As such, to add new environment variables to an environment, simply add a new file inside the environment directory. This is useful if your environments contain some files that need to be ignored by VCS:

$ tree -a <project-root>/environments

configuration-test/environments
├── dev
│   ├── .db-secrets.env     ## Ignored by Git
│   └── .emily.env
└── prod
    ├── .auth-secrets.env   ## Ignored by Git
    ├── .db-secrets.env     ## Ignored by Git
    └── .emily.env