Some gemstash configurations don't have a /home/gemstash directory (e.g. minimal Docker installations), and prefer to store their Gemstash configuration elsewhere (e.g. in a system-wide location such as /etc/gemstash/config.yml). Today, such use-cases require every Gemstash command to be accompanied by the --config-file CLI option, and forgetting to do so causes Gemstash to use its default settings.
This PR resolves #369, smoothing the wrinkles for this use-case, by supporting defining the path to one's configuration in the GEMSTASH_CONFIG environment variable.
Some gemstash configurations don't have a
/home/gemstash
directory (e.g. minimal Docker installations), and prefer to store their Gemstash configuration elsewhere (e.g. in a system-wide location such as/etc/gemstash/config.yml
). Today, such use-cases require every Gemstash command to be accompanied by the--config-file
CLI option, and forgetting to do so causes Gemstash to use its default settings.This PR resolves #369, smoothing the wrinkles for this use-case, by supporting defining the path to one's configuration in the
GEMSTASH_CONFIG
environment variable.