If you find yourself passing the same options to Terminus repeatedly, consider creating a configuration file to provide default values for common options. The Terminus configuration file lives at
Any command variable normally passed in the form of
--option=VALUE is configurable. Values stored will be available regardless of which alias you use to run the command. Default values stored this way will be overridden by those supplied on the command line.
You can see all the available options for a given command (e.g., available
--format options) by running it with the
--help option in your terminal:
$HOME/.terminus/config.yml file uses YAML formatting, which relies on indentation in the form of two spaces per indent:
command: auth: login: options: email: email@example.com hide_git_mode_warning: 1 site: pancakes: options: app: sequelpro
The example above does three things:
When the command
terminus auth:loginis run, it will automatically provide the correct email address. This is useful if you find yourself logging in to multiple accounts frequently, and want to use your regular account by default.
Terminus will warn you when running commands in an environment set to Git mode, unaware if the command affects the codebase or not:
[warning] This environment is in read-only Git mode. If you want to make changes to the codebase of this site (e.g. updating modules or plugins), you will need to toggle into read/write SFTP mode first.
TERMINUS_HIDE_GIT_MODE_WARNINGdisables that message, which is useful for those using Terminus for frequent changes to files, not code.
The Terminus Plugin Pancakes lets you open your Pantheon site database with a SQL GUI client. Rather than define the app every time, this configuration will always use Sequel Pro, unless otherwise specified.