Lono’s behavior can be tailored using a
settings.yml file. This file should be created at
configs/settings.yml within the project. The options from the files get merged with the following precedence:
- current folder - The current folder’s
configs/settings.ymlvalues take the highest precedence.
- user - The user’s
~/.lono/settings.ymlvalues take the second highest precedence.
- default - The default settings bundled with the tool takes the lowest precedence.
Let’s take a look at an example
# The base config is specially treated. It gets included the other environments automatically. base: # extract_scripts: # to: "/opt" # as: "ec2-user" # stack_name_suffix: random # tack on a 3 char random string at the end of the stack name for lono cfn create development: # The aws_profile tightly binds LONO_ENV to AWS_PROFILE and vice-versa. # aws_profile: dev_profile production: # The aws_profile tightly binds LONO_ENV to AWS_PROFILE and vice-versa. # aws_profile: prod_profile
The table below covers what each setting does:
|aws_profile||This provides a way to tightly bind
|extract_scripts||This configures how the
Pro tip: Use the <- and -> arrow keys to move back and forward.