ytools 0.1.0 → 0.1.1

data/README.markdown

@@ -0,0 +1,76 @@
+# YTools
+
+These are a couple of YAML-based tools for working with configuration files.
+
+### YPath
+
+The first tool, ypath, be used to pull values from a YAML configuration and print
+them to STDOUT.  It's quite useful if you need to use the YAML as a configuration
+and only pull out individual values for your other scripts to use.
+
+Say you have a YAML configuration file like:
+
+    project:
+        name: C.proj
+        dependencies:
+            - A.proj
+            - B.proj
+
+You could then pull out the project name 'C.proj' by running
+
+    ytools -p /project/name YAML_FILE
+
+You could even list all of the dependencies by running
+
+    ytools -p /project/dependencies YAML_FILE
+
+which would print
+ 
+    A.proj
+    B.proj
+
+### YTemplates
+
+The second tool, ytemplates, be used to generate configuration files
+that use YAML files as the backing object binding.  A simple use case might
+be that you need a configuration file generated for an environment, and you
+can break out the environment-specific values into different YAML files.
+In this case, you could create a file for each environment, one for production
+
+    environment: production
+    database:
+        host: production.host.com
+        username: produser
+        password: imsecret
+
+and another for testing
+
+    environment: testing
+    database:
+        host: internal-testing.host.com
+        username: testuser
+        password: imsecret
+
+With those files, you could then create an ERB template to pull in the relevant
+values like:
+
+    <settings environment="<%= environment =>">
+        <database>
+            <host><%= database.host %></host>
+            <username><%= database.username %></username>
+            <password><%= database.password %></username>
+        </database>
+    </settings>
+
+Using ytemplates, you could then generate a different environment
+file from each yaml file, but only have to manage one actual configuration file.
+Obviously, this becomes much more useful when the number of environments grows
+and the number of changes in the configuration files goes down relative to file's
+size.
+
+## Downloading
+
+You can download the gem using
+
+    gem install ytools
+

data/lib/VERSION

@@ -1 +1 @@
-0.1.0
+0.1.1

data/lib/ytools/path/cli.rb

@@ -14,7 +14,8 @@ module YTools::Path
           STDERR.puts executor.yaml_object
         end
 
-        puts executor.process!
+        output = executor.process!
+        puts output if !output.empty?
       rescue YTools::Path::ParseError => e
         print_path_error(e)
       end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: ytools
 version: !ruby/object:Gem::Version 
-  hash: 27
+  hash: 25
   prerelease: false
   segments: 
   - 0
   - 1
-  - 0
-  version: 0.1.0
+  - 1
+  version: 0.1.1
 platform: ruby
 authors: 
 - Gabe McArthur
@@ -42,9 +42,10 @@ executables:
 - ytemplates
 extensions: []
 
-extra_rdoc_files: []
-
+extra_rdoc_files: 
+- README.markdown
 files: 
+- README.markdown
 - Rakefile
 - bin/ypath
 - bin/ytemplates