Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Modify your ENV

Subscribe to updates I use climate_control

Statistics on climate_control

Number of watchers on Github 216
Number of open issues 1
Average time to close an issue 2 months
Main language Ruby
Average time to merge a PR 27 days
Open pull requests 3+
Closed pull requests 7+
Last commit almost 3 years ago
Repo Created about 7 years ago
Repo Last Updated almost 2 years ago
Size 39 KB
Organization / Authorthoughtbot
Page Updated
Do you use climate_control? Leave a review!
View climate_control activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating climate_control for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

Climate Control

Easily manage your environment.


Add this line to your application's Gemfile:

gem 'climate_control'

And then execute:

$ bundle

Or install it yourself as:

$ gem install climate_control


Climate Control can be used to temporarily assign environment variables within a block:

ClimateControl.modify CONFIRMATION_INSTRUCTIONS_BCC: '' do
  sign_up_as ''
  confirm_account_for_email ''
  current_email.should bcc_to('')

To use with RSpec, you could define this in your spec:

def with_modified_env(options, &block)
  ClimateControl.modify(options, &block)

This would allow for more straightforward way to modify the environment:

require 'spec_helper'

describe Thing, 'name' do
  it 'appends ADDITIONAL_NAME' do
    with_modified_env ADDITIONAL_NAME: 'bar' do
      expect( eq('John Doe Bar')

  def with_modified_env(options, &block)
    ClimateControl.modify(options, &block)

To modify the environment for an entire set of tests in RSpec, use an around block:

describe Thing, 'name' do
  # ... tests

  around do |example|
    ClimateControl.modify FOO: 'bar' do

Environment variables assigned within the block will be preserved; essentially, the code should behave exactly the same with and without the block, except for the overrides. Transparency is crucial because the code executed within the block is not for ClimateControl to manage or modify. See the tests for more detail about the specific behaviors.

Why Use Climate Control?

By following guidelines regarding environment variables outlined by the twelve-factor app, testing code in an isolated manner becomes more difficult:

  • avoiding modifications and testing values, we introduce mystery guests
  • making modifications and testing values, we introduce risk as environment variables represent global state

Climate Control modifies environment variables only within the context of the block, ensuring values are managed properly and consistently.


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request


climate_control is copyright 2012-2017 Joshua Clayton and thoughtbot, inc. It is free software and may be redistributed under the terms specified in the LICENSE.txt file.

climate_control open issues Ask a question     (View All Issues)
  • over 3 years ERROR: Error installing climate_control: activesupport requires Ruby version >= 2.2.2
  • about 4 years Modifiers on before and after
climate_control open pull requests (View All Pulls)
  • Create RSpec metadata
  • Document lack of thread safety
  • Remove activesupport dependency
climate_control list of languages used
Other projects in Ruby