It would help developers using .env files to fine-tune their local development experience for Calliope to support global (that is: project non-specific) configuration that they can keep in a single location (their $HOME?) and have it take effect in all of their projects.
Proposed Solution
Have Calliope load ~/.env.calliope first, then load the current project’s .env file as an override.
Alternatives Considered
n/a
Additional Context
This is particularly useful for developers to like to have linting automatically turned on during development. As it currently stands, these devs are forced to create a .env file on every project that uses this tool (or the original toolchain it was based on). Since this is the kind of behavior devs are likely to want to configure globally, it makes sense to make it easy to do so from a single place.
Description
It would help developers using
.envfiles to fine-tune their local development experience for Calliope to support global (that is: project non-specific) configuration that they can keep in a single location (their$HOME?) and have it take effect in all of their projects.Proposed Solution
Have Calliope load
~/.env.calliopefirst, then load the current project’s.envfile as an override.Alternatives Considered
n/a
Additional Context
This is particularly useful for developers to like to have linting automatically turned on during development. As it currently stands, these devs are forced to create a
.envfile on every project that uses this tool (or the original toolchain it was based on). Since this is the kind of behavior devs are likely to want to configure globally, it makes sense to make it easy to do so from a single place.