exportr 0.1.2 → 0.1.3

data/LICENSE

@@ -0,0 +1,8 @@
+Copyright (C) 2012 Richard Calahan, All Day Everyday
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software
+and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,43 @@
+
+# Exportr: Environment manager for Rails development
+
+## Description
+
+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, 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. But you probably also hard code
+'default' options to default to on your local machine. Hardcoding default configuation options, especially private keys 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 a local yaml file. 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.  
+
+### Setup
+
+Add the gem to your Gemfile.
+
+    gem 'exportr'
+
+Install it!
+
+    $ bundle install
+    
+Run the generator.
+
+    $ rails generate exportr
+    
+
+The generator creates a yaml file in your config directory. It will store key:value pairs to be loaded as environment variables when your app launches. You can edit it manually, or use the command line utility.
+
+### CLI
+
+There are two simple options for use with the command line tool: **add** and **remove**.  
+You can use flags longform `--add` or shorhand `-a`.
+
+    $ exportr --add KEY=VALUE
+or
+
+    $ exportr --remove KEY
+    
+### FYI

data/lib/exportr/version.rb

@@ -1,3 +1,3 @@
 module Exportr
-  VERSION = "0.1.2"
+  VERSION = "0.1.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: exportr
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-03-29 00:00:00.000000000 Z
+date: 2012-03-30 00:00:00.000000000 Z
 dependencies: []
 description: Helps manage rails application specific environment variables for multiple
   apps in development.
@@ -22,7 +22,8 @@ extra_rdoc_files: []
 files:
 - .gitignore
 - Gemfile
-- README
+- LICENSE
+- README.md
 - Rakefile
 - bin/exportr
 - exportr.gemspec

data/README

@@ -1,15 +0,0 @@
-Finally, you can configure local environment variables for each of your rails apps. 
-
-Simple.
-
-Gemfile:
-
-gem 'exportr'
-
-CLI:
-
-rails generate exportr
-
-Add environment variables to config/exportr.yml:
-
-FACEBOOK_APP_ID: '124323434564'