Setting environment variables with puppet

ruby deployment environment-variables environment puppet
Jake232 picture Jake232 · Mar 15, 2013 · Viewed 11.6k times · Source

I'm trying to work out the best way to set some environment variables with puppet.

I could use exec and just do export VAR=blah. However, that would only last for the current session. I also thought about just adding it onto the end of a file such as bashrc. However then I don't think there is a reliable method to check if it is all ready there; so it would end up getting added with every run of puppet.

Answer

myitcv picture myitcv · Mar 15, 2013

I would take a look at this related question.

*.sh scripts in /etc/profile.d are read at user-login time (as the post says, at the same time /etc/profile is sourced)

Variables export-ed in any script placed in /etc/profile.d will therefore be available to your users.

You can then use a file resource to ensure this action is idempotent. For example:

file { "/etc/profile.d/my_test.sh":
  content => 'export MYVAR="123"'
}

Related questions

Capistrano SSH::AuthenticationFailed, not prompting for password

I've been using capistrano successfully for a while now and all of a sudden in every project I've lost the ability to deploy. Environment: os X (Mavericks) ruby 1.9.3p194 rvm (locally, not on server) rails 3.2 and up RubyGems 1.8.25 I'm not …

Read More
bundle install doesn't work from capistrano

I want to deploy my simple rails 4.0 application via capistrano 3.0. I use bundler 1.3.5 so I add capistrano-bundler gem to integrate bundler with capistrano. I have pretty simple configuration (almost default): set :bundle_gemfile, -> { release_path.join('Gemfile') } set :…

Read More
Unicorn unable to write pid file

I am using deploying a Ruby on Rails app to a Linode VPS using Capistrano. I am using Unicorn as the application server and Nginx as the proxy. My problem is that I am not able to start Unicorn because …

Read More