Developer Documentation

Configuration Directory

The envirobly directory, in your project’s root, is where all the deployment configuration lives. It consists of YAML and plain text files. All of them you can edit by hand.

Structure

.envirobly/
  .targets/ # Created after the first deploy
    .default/ # Default deploy target settings
      account_url
      project_name
      region
  deploy.yml # Base configuration file
  deploy.{environ-name}.yml # Configuration override per environ

Generally, you should keep your configuration under version control.

Validation

At any time, you can validate your environ specific configuration:

# Validate deploy.yml
envirobly validate

# Validate deploy.yml + deploy.production.yml
envirobly validate production

You don’t need to commit changes to the configuration before validating it; or deploying with it.

Changing default deployment target

After your first deployment, a .default target is created within .envirobly/.targets/, that saves the information about where you’ve deployed, so that you don’t have to specify these settings with every deploy.

You can change the default target settings:

envirobly target

You’ll interactively choose the account, project name and region. Defaults are provided, pulled from your existing configuration if present.

Removing Defaults

To purge all defaults, execute from within your project’s root directory:

rm -rf .envirobly/.targets/.default

During your next deployment, you’ll be asked to choose new defaults.