gen-env 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 750b5e7ac9d357a396ebae94c0ce940067423501
-  data.tar.gz: f999d70448165b9ceb54f263413fb3e2868e38a6
+  metadata.gz: 2992a034494a57a27f8a19cdf9b3f0633d8d972b
+  data.tar.gz: a986f86ab014b1047b3fe9ac1e516a3d22b63c6f
 SHA512:
-  metadata.gz: 33b14787ddbab577f6f9a4aab0bdc95e4ea98c0f6f5ce5465e27ca3a6c1923e0ef0707cbe72fd86310f695b23f2ad37fdf65d1c1ca7e14e9fa58f6724dbcc373
-  data.tar.gz: 9a56106be0b670f427d0d2d199507e1d9d9d4a9eaa1620d3587dd128c2c15e33ca7ffbaee6b2f6872f964491779cc0b7cabb272f2704de82a067f9205c24adbb
+  metadata.gz: 45e4e29c4c6bfb332fbb9c4d858c8bdec8431a5cb04e002807c09392a845007a67e907cde9590ef93bcc7d2b72e8d6a723bb3bfee4810c50220d3fb539130e69
+  data.tar.gz: 2328eb1f7540c93257f11fdc6910cf7d56ddec33a3d04a0794dde4e673721f488a12ca6d56e27b6b33a44d64dd686b064ce21fe460ed1d2633d0cf5b2549b80d

data/README.md

@@ -2,15 +2,15 @@
 
 More than often, a typical java project requires you to manage multiple properties or env files across different environments. For example, local.env, sit.env, qa.env etc etc. And there are multiple problems managing these sort of environment files.
 
-#### Problems with multiple .properties file
+#### Problems with multiple .properties/.env files
 
-1. No better mechanism of logically grouping multiple entries in .env file, other than developer's discipline. For example, order of individual configurations for database, load-balancer etc. can vary a lot from one environment to other.
-2. It becomes difficult and cumbersome to find a single entry in all properties file and change it without juggling with your favorite editor's find and replace feature.
-3. No way of testing if a particular variable is available in the corresponding .env / .properties file other than manually doing grep on the file. This can cause lots of surprises when you actually deploy an app in environment.
+1. No better mechanism of logically grouping multiple key/value pairs in .properties/.env file, other than developer's discipline. For example, order of individual configurations for database, load-balancer etc. can vary a lot from one environment's configuration file to other's.
+2. It becomes difficult and cumbersome to find a single key/value pair in all .properties/.env file and change it without juggling with your favorite editor's find and replace feature.
+3. No way of testing if a particular key/value pair is available in the corresponding .properties/.env file other than manually doing grep on the file. This can cause lots of surprises when you actually deploy an app in environment.
 
 #### Solutions to above problems
-1. A simple DSL that can logically group different configurations and produce the final env / property file in same order across multiple environment.
-2. Rather than managing .env / .properties files in plain text files, an ability to write your .env / .properties in ruby language allows you to unit test your configuration files for presence or absense of particular key/value pair.
+1. A simple DSL that can logically group different configurations and produce the final .properties/.env file having same order of key/value pair for different configurations across multiple environments.
+2. Rather than managing .properties/.env files in plain text files, an ability to write your configurations in ruby language allows you to unit test your configuration files for presence or absense of particular key/value pair.
 
 ## Installation
 

data/lib/gen/env/version.rb

@@ -1,5 +1,5 @@
 module Gen
   module Env
-    VERSION = "0.2.1"
+    VERSION = "0.2.2"
   end
 end

data/lib/parser.rb

@@ -7,7 +7,7 @@ class Parser
     options = {}
     opt_parser = OptionParser.new do |opt_parser|
       
-      opt_parser.banner = "Usage: generate_env --in /path/to/input/environment.rb --out /path/to/output/environment.env" 
+      opt_parser.banner = "Usage: gen-env --in /path/to/input/environment.rb --out /path/to/output/environment.env" 
       
       opt_parser.on("-iNAME", "--in INPUT_FILE", "Input ruby file path") do |input_environment_file_path|
         options[:input_environment_file_path] = input_environment_file_path

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gen-env
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - Dhanesh Arole