Adding support for server environment variables in deploy.rb, (:env_vars)

[pricees]

Users may specify environment variables, as a string, to be passed to the ssh commands.

Idea: Our app is ported from a heroku environment. To use nina effectively, in the 12-factor-app paradigm, we need to be able to pass values at deploy time.

# deploy.rb

set :env_vars, "foo=1 bar=baz"

# .env stores key-value pairs
set :env_vars, { File.open(".env").readlines.map(&:chomp).join(" ") }

[pedroassumpcao]

Nice stuff.

[fnando]

+1

[aoqfonseca]

+1

[brain-geek]

+1

[mhluska]

+1

[mhluska]

This doesn't seem to be working. I'm getting:

bash: line 0: export: `-t': not a valid identifier
       bash: line 0: export: `--': not a valid identifier
       bash: line 0: export: `-----> Using RVM environment 'ruby-2.1.5@default'': not a valid identifier

Using the --simulate flag gives:

#!/usr/bin/env bash
# Executing the following via 'ssh [...] -p [...] export RACK_ENV=production -t':
#

[pricees]

Not sure under what context you are using it. Also, it's been a year since that pull request, have things changed?

[mhluska]

Unless I'm missing something, $ ssh [hostname] -p [port] export RACK_ENV=production -t is invalid syntax.

[pricees]

:( --- It worked. Once. My contribution is for not. Close the PR, then.

[d4be4st]

Fixed it, moved the env_vars to the top of the commands list so it would set the env_vars before anything.

[pricees]

Awesome. Thanks.
On Jan 24, 2015 12:23 AM, "štef" [email protected] wrote:

Fixed it, moved the env_vars to the top of the commands list so it would
set the env_vars before anything.

—
Reply to this email directly or view it on GitHub
#161 (comment).