This release adds an --erb-configuration option to allow the use of ERB templating instead of a plain JSON configuration file.
This allows a way to keep passwords, and other sensitive information out of configuration files.
An ERB template file (config.json.erb) might look like:
{
"accounts": [
{
"username": "user@example.com",
"password": "<%= ENV['IMAP_PASSWORD'] %>",
"server": "imap.example.com"
}
]
} N.B. As the Ruby code in the ERB blocks is executed, this approach introduces the risk of arbitrary code execution, so an ERB template configuration modifiable by a third party should be carefully vetted before being used.