Lita Dotenv Config Loader

lita_dotenv is designed to allow storing an entire Lita bot config in an .env file including the following:

• map environment variables to Lita config properties
• coerce environment variable value types to Ruby types
• load .env file if exists

The lita_config.rb file should be as simple as:

require 'lita_dotenv'

Lita.configure do |config|
  config = LitaDotenv.new(config).config
end

Add lita_dotenv to your Lita instance's Gemfile:

gem "lita_dotenv"

DotenvConfig uses a simple parser that follows the following rules for assigning ENV variable names to Lita paths:

1. all paths begin with LITA_
2. all paths are designed to match Lita configure paths
3. optional type coercion is available by setting the type as a suffix:
4. Symbol: __TYPESYM
5. Boolean: __TYPEBOOL
6. Integer: __TYPEINT
7. JSON: __TYPEJSON
8. JSON with symbole keys: __TYPEJSONSYM
9. underscores are handled in paths by using camelCase starting with a lowercase letter where an underscore is inserted before each uppercase letter

LITA_ROBOT_NAME=Configbot          # config.robot.name = 'Configbot'
LITA_ROBOT_LOCALE__TYPESYM=en      # config.robot.locale = :en
LITA_ROBOT_logLevel__TYPESYM=info  # config.robot.log_level = :info

In the ideal case, the lita_config.rb file should be as simple as:

require 'lita_dotenv'

Lita.configure do |config|
  config = LitaDotenv.new(config).config
end

• Map config hash key values, e.g. config.redis[:url]

See CHANGELOG.md

Project Repo

• https://github.com/grokify/lita_dotenv

Lita

• https://www.lita.io/

1. Fork it ( http://github.com/grokify/lita_dotenv/fork )
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

Lita Dotenv Config Loader is available under the MIT license. See LICENSE.txt for details.

Lita Dotenv Config Loader © 2016 by John Wang