No commit activity in last 3 years
No release in over 3 years
A utility method for using dotenv as a configuration manager
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Development

~> 1.3
>= 0

Runtime

>= 0.10
 Project Readme

dotenv-configuration

A utility method for using dotenv as a configuration manager

wercker status

Installation

Add this line to your application's Gemfile:

gem 'dotenv-configuration'

And then execute:

$ bundle

Or install it yourself as:

$ gem install dotenv-configuration

Usage

require 'dotenv-configuration'
Dotenv.configure(
  'TWITTER_API_KEY' => 'default value',
  'TWITTER_API_SECRET' => 'default value', 
)

Dotenv.configure will call Dotenv.load internally.

if .env file or 'TWITTER_API_KEY' is empty, $EDITOR will spin up and you can set these keys as pit.gem.

See also

Thanks

Original idea from @linyows

Contributing

Usual GitHub way.

  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