exportr 0.2.5 → 0.2.6

data/README.md

@@ -4,11 +4,11 @@
 
 Managing environment variables locally is kind of a drag. If you only build one application at a time, you *could* simply export environment variables in your .bashrc. But in reality you're working on 5 apps at a time, each requiring different settings for Facebook, Google, AmazonS3, etc. 
 
-You probably set environment variables on your production servers to store configuration options for these services. Yet you might also hard code 'default' options to fall back to on your local machine. Hardcoding default configuation options, especially private keys and passwords for third party apis is an *insane* security risk.
+If you set environment variables on your production servers to store configuration options for these services, you might also hard code 'default' options to fall back to on your local machine. Hardcoding default configuation options, especially private keys and passwords for third party apis is an *insane* security risk.
 
 **Problem solved**.
 
-Exportr helps you manage local environment variables. Each set is scoped to a specific rails application in `config/exportr.yml`. The file is 'git ignored' when created, so it never leaves your machine. Its key:value pairs are loaded as environment variables when your application initializes.  
+Exportr helps you manage *local* environment variables. Each set is scoped to a specific rails application in `config/exportr.yml`. The file is 'git ignored' when created, so it never leaves your machine. Its key:value pairs are loaded as environment variables right before your application initializes.  
 
 ### Setup
 
@@ -28,16 +28,33 @@ The generator creates a yaml file in your config directory. It will store key:va
 
 ### CLI
 
-There are four simple options for use with the command line tool: **add**, **remove**, **clear** and **list**.  
-You can use flags longform `--add, --remove, --clear, --list` or shorhand `-a, -r, -c, -l`.
+You can edit the yaml config file directly, or use the handy CLI. There are several simple options for managing your configuration.  
+You can use flags longform *e.g.* `--add, --remove, --clear, --list` or shorhand *e.g.* `-a, -r, -c, -l`.
+
+**Add**
 
     $ exportr --add KEY=VALUE
 
+**Remove**
+
     $ exportr --remove KEY
-    
+
+**Clear**    
+
     $ exportr --clear
-    
+
+**List**
+
     $ exportr --list
+
+**Version**
+
+    $ exportr --version
+
+**Help**
+
+    $ exportr --help
+
     
 ### FYI
 

data/lib/exportr/railtie.rb

@@ -8,7 +8,7 @@ module Exportr
 
     config.before_initialize do
       if File.exists? config_file
-        config = YAML.load(File.open(config_file)
+        config = YAML.load(File.open(config_file))
         config.each_pair { |key,value| ENV[key] = value } if config
       end
     end

data/lib/exportr/version.rb

@@ -1,3 +1,3 @@
 module Exportr
-  VERSION = "0.2.5"
+  VERSION = "0.2.6"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: exportr
 version: !ruby/object:Gem::Version
-  version: 0.2.5
+  version: 0.2.6
   prerelease: 
 platform: ruby
 authors: