You are browsing upcoming documentation for version 6.1 of OroCommerce, scheduled for release in 2025. Read the documentation for version 6.0 (the latest LTS version) to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

How to Add/Remove Environment Variables 

Environment variable can be configured for application usage, as illustrated below:

      COMPOSER_AUTH:  '{"http-basic":{"":{"username":"username","password":"password"}}'
      COMPOSER_AUTH1: '{"gitlab-oauth":{"":"ThisTokenIsNotSoSecretChangeIt"},"gitlab-domains":[""]}'
      COMPOSER_AUTH2: '{"gitlab-oauth":{"":"ThisTokenIsNotSoSecretChangeIt"}}'
      COMPOSER_AUTH3: '{"gitlab-token":{"":"ThisTokenIsNotSoSecretChangeIt"},"gitlab-domains":[""]}'
      COMPOSER_AUTH4: '{"gitlab-token":{"":"ThisTokenIsNotSoSecretChangeIt"}}'
      COMPOSER_AUTH5: '{"github-oauth":{"":"ThisTokenIsNotSoSecretChangeIt"}}'
  • env_vars — the hash where the key is an environment variable name, and the value is the environment variable value.

How to Configure Environment Type Based Application 

      'ORO_DEPLOYMENT_TYPE': 'local'
  • local - deployment_type, which will be set to parameters.yml for your deployed application as

deployment_type: local


For more details on the environment type based application configuration, please see the related documentation in the backend developer guide.


Environment variables are always string and are not cast automatically to integer, null, or other types. You should never pass an empty environment variable, like ‘ORO_DB_HOST=’ or ‘ORO_DB_HOST=NULL’. Instead, it should never be available (never be set). More information about environment variables is available in the parameters.yml description section.