Mina has a feature which allows overriding variables (set using set method) with environment variables, e.g. rails_env=production mina deploy will override rails_env variable set in config/deploy.rb. While this is a useful feature, it also causes unexpected issues.
For example, one variable Mina uses is called user. Windows environments have a USER environment variable, however, since they're case-insensitive, it can be accessed as lowercase user, so it will override a Mina-set user variable.
Instead of environment variables, we should find another way of supporting variables through CLI. One of the proposed solutions is to take an approach similar to that of docker run command, which accepts variables as an option (see docs). The above example command would then look like this: mina deploy --env rails_env=production.
Mina has a feature which allows overriding variables (set using
setmethod) with environment variables, e.g.rails_env=production mina deploywill overriderails_envvariable set inconfig/deploy.rb. While this is a useful feature, it also causes unexpected issues.For example, one variable Mina uses is called
user. Windows environments have aUSERenvironment variable, however, since they're case-insensitive, it can be accessed as lowercaseuser, so it will override a Mina-setuservariable.Instead of environment variables, we should find another way of supporting variables through CLI. One of the proposed solutions is to take an approach similar to that of
docker runcommand, which accepts variables as an option (see docs). The above example command would then look like this:mina deploy --env rails_env=production.