Project

configs

0.01
Low commit activity in last 3 years
No release in over a year
Easy (easier?) management of config/*.yml files. Defines a lookup priority for the current environment's settings.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Dependencies

Development

>= 0
> 4, < 5.19

Runtime

 Project Readme

Configs

Test and Release

Loads and manages config/*.yml files.

Searches through a few locations to find the right environment config:

  1. config/$name/$env.yml
  2. config/$name.yml (with $env key)
  3. config/$name/default.yml
  4. config/$name.yml (with 'default' key)

Installation

Add this line to your application's Gemfile:

gem 'configs'

And then execute:

$ bundle

Or install it yourself as:

$ gem install configs

Usage

If you have a config/foo.yml, then anywhere you need to read the file you can use Configs[:foo] as a hash.

Example:

# config/foo.yml
development:
  hello: world

# Elsewhere (even in a config/initializer)
Configs[:foo][:hello]
=> 'world'

You can include ERB in the YAML files:

# config/foo.yml
development:
  database_password: <%= ENV['DATABASE_PASSWORD'] %>

Contributing

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

License

Copyright 2014 Kickstarter, Inc

Released under an MIT License