habitat 
Version 0.4.0
Library for managing your environment vars.
Why
According to factor 3, you should be
storing your configuration as environment variables. Writing
process.env
everywhere can be real annoying, so this abstracts away of
that manipulation. It also provides some nice little nicities for testing.
Installation
Why NPM of course!
$ npm install habitat
Usage
new habitat([prefix, [defaults]])
Creates a new environment manipulator.
prefix
is the prefix for your environment variables. For example, if
your app is called airsupport
, it's probably good to namespace your
environment variables like so:
export AIRSUPPORT_HOST='lolcathost'
export AIRSUPPORT_PORT=3000
export AIRSUPPORT_WEBSOCKETS=true
In this case, you would use new habitat('airsupport')
-- the prefix will be
auto-capitalized because only barbarians use lowercase letters in their
environment variables.
defaults
is an object representing the defaults if a key cannot be
found in the environment. This should be used sparingly.
var env = new habitat('airsupport', { port: 1024 })
var port = env.get('port');
habitat#get(key, [default])
Gets a key from the environment. Automatically prefixes with the
prefix
passed to the constructor, if necessary.
habitat#get
will also try to do some parsing of the value if it looks
like a boolean
, number
or json
, so you can do things like this:
export APP_ADMINS='["me@example.com", "you@example.com"]'
var env = new habitat('app');
var admins = env.get('admins');
console.log(admins.indexOf('you@example.com'))
If a default
is passed, if the key is undefined in either the env or
the constructor-set defaults, it will fall back to that.
Getting objects
get
will automatically return objects if you take advantage of common prefixing:
export APP_DB='redis'
export APP_REDIS_HOST='127.0.0.1'
export APP_REDIS_PORT=6379
var env = new habitat('app');
var db = env.get('db');
var options = env.get(db);
console.log(options.host);
console.log(options.port);
Getting keys using camelCase
You can also use camelcase instead of underscores if you want, habitat's
got your back.
export APP_SOME_LONG_KEY='great'
var env = new habitat('app');
console.log(env.get('someLongKey'))
habitat.get(key)
You can also use get
directly from the habitat object to get
unprefixed things from the environment.
var path = habitat.get('path');
var nodeEnv = habitat.get('nodeEnv');
habitat.load([pathToEnvFile])
Try to load a set of environment variables from a file. Will not
overwrite existing environment variables if there is a conflict.
export PARAMETER_ONE=one
export PARAMETER_TWO=two
habitat.load('/some/directory/.env');
console.dir(habitat.get('parameter'));
pathToEnvFile
defaults to '.env'
, which will just look for a .env
file in the current working directory.
habitat#set(key, value)
Sets an environment variable, with prefix if passed.
habitat#unset(key)
Unsets an environment variable
habitat#all()
Get an object with all of the things in the environment.
Example:
export APP_HOST='localhost'
export APP_PORT=3000
export APP_PROTO=http
var env = new habitat('app');
var obj = env.all();
console.log(obj.host);
habitat#temp(object, callback)
Temporarily overrides environment variables with values from object
.
callback
can be syncronous if defined without any parameters, or async
if defined with a single parameter.
Example:
var env = new habitat('airsupport', {
protocol: 'http',
host: 'airsupport.io',
port: 3000
});
var tempEnv = {
host: 'lolcathost'
port: 5000
};
env.temp(tempEnv, function() {
console.log(env.get('host'))
console.log(process.env['AIRSUPPORT_HOST'])
})
console.log(env.get('host'))
env.temp(tempEnv, function(done)
process.nextTick(function(){
console.log(env.get('port'))
done();
});
})
License
MIT