HomePricing
Search…
Welcome to Release
Getting started
Prepare to Use Release
Create Your Application
Guides and examples
Onboarding Guides
Example applications
Running Instances
Advanced guides
Reference documentation
Admin / Account Settings
Workflows in Release
Release Environment Versioning
Application Settings
End-to-End Testing
Environment Settings
Environment Expiration
Instant Datasets
Static Service Deployment
Helm
GitOps
The .release.yaml file
Docker Compose Conversion Support
Reference Examples
Release API
Background concepts
How Release Works
Frequently Asked Questions
AWS Support FAQs
Docker Support FAQs
JavaScript Support FAQs
Integrations
Integrations Overview
Source Control Integrations
CLI
Getting Started
Installation
Configuration
CLI Usage Example
Command Reference
Powered By GitBook
Configuration
Configuration options for the Release CLI

Overview

By default, release will store its configuration file at $HOME/.release.yaml. There are two methods for overriding the default configuration:
  1. 1.
    Set the RELEASE_CONFIG environment variable to another file path containing your configuration.
  2. 2.
    Provide the path to a different configuration file to the --config flag as part of a command.

Settings

The configuration file contains the following settings fields, which will be used globally unless overridden:
  • account (optional): The name or ID of the default Release account
  • app (optional): The name or ID of the default Release app
If you would like to avoid specifying the --account flag on each release command, update your $HOME/.release.yaml with the following:
1
account: YOUR_ACCOUNT_NAME
Copied!
Optionally, you can set this through the environment variable, as specified below.

Environment variables

Any setting can be overriden by an environment variable named RELEASE_<KEY>. For example, to override account, set RELEASE_ACCOUNT=MyAccount.
CLI - Previous
Installation
Next - CLI
CLI Usage Example
Last modified 28d ago
Copy link
Contents
Overview
Settings
Environment variables