How to ENV variables about mina

[simonc]

Maybe you can set the bundle_bin variable to add the environment variables:

set :bundle_bin, 'GUSER=xxx GPASS=yyy bundle'

[lulalala]

@rstacruz

May I ask is there a doc for task :env do? It does not append ENV setting in the command.

I used set :bundle_prefix to achieve this.

[pricees]

Can you believe there is still no environment variable option? Goodness grief! Well, I think we may fork this thang and add an env-var option but until then we are using a big time hack.

We store our variables locally in an .env file

under the settings we put:

# Non-cowboys, don't try this in production.
set :ssh_options, %{export #{File.open(".env").readlines.map(&:chomp).join(" ")}}

You get the gist and can make it pretty yourself. This is one way to Heroku-tize our deploy.

Happy hacking,
Best.
Ted

[AldanaQuintana]

@lulalala thanks, it worked for me!

I set bundle_prefix like this:

set :bundle_prefix, 'env $(cat .env | xargs) bundle exec '

[simonc]

I agree, an environment_variables should be available to provide variables shared across commands while deploying.

[misteral]

set :bundle_bin, 'GUSER=xxx GPASS=yyy bundle'

this is OK !!!! Thanks

[rstacruz]

Try:

task :env do
queue %[NAME="hello"]
end

On Oct 30, 2012, at 6:11 PM, Simon COURTOIS [email protected]
wrote:

I agree, an environment_variables should be available to provide variables
shared across commands while deploying.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/65#issuecomment-9900324.

[rstacruz]

As stated earlier, this should work:

task :env do
   queue %[NAME="hello"]
end

[rstacruz]

Also, if you want to put it in .bashrc instead (IMHO a much better idea!), you should export the variables:

# .bashrc
export NAME="hello"

[phanhaiquang]

I use Figaro

require 'yaml'

set :var_from_env, -> { YAML.load_file("./config/application.yml")["ENV_VAR"] }