gardener 1.1.5 → 1.2.0

data/README.rdoc

@@ -6,7 +6,7 @@ Gardener is intended to be used from the rails console, although I suppose you c
 
 ==Usage
 Put
-	gem 'gardener'
+  gem 'gardener'
 in your gemfile and gardener gets right to work.
 
 He's there behind the scenes and you can call on him in several ways.
@@ -14,8 +14,8 @@ He's there behind the scenes and you can call on him in several ways.
 ==Instance Methods
 
 ===plant_seed
-	c = Content.first
-	c.plant_seed
+  c = Content.first
+  c.plant_seed
 
 This is the use case I wrote Gardener to solve.
 
@@ -97,7 +97,7 @@ You can add 'z' to any of the above responses and Gardener will apply that respo
 
 
 ===sow
-	User.sow
+  User.sow
 Will plant all the User records in the garden, which you can commit to your (D)VCS and deploy wherever.
 
 

data/lib/gardener.rb

@@ -1,5 +1,5 @@
 module Gardener
-  
+
 
   def self.included(base)
     base.extend(ClassMethods)
@@ -8,8 +8,8 @@ module Gardener
   module ClassMethods
 
     attr_accessor :infinite_choice
-    
-    # Deletes the file associated with this class, so you can plant new seeds.  Should be done once per growing season.  
+
+    # Deletes the file associated with this class, so you can plant new seeds.  Should be done once per growing season.
     def harrow
       File.delete(garden_path)
     end
@@ -29,7 +29,7 @@ module Gardener
     def garden_path
       File.join([Rails.root, 'db', 'garden', "#{self.to_s.underscore.pluralize}.yml"] )
     end
-    
+
     # Loads each yaml representation of an object up into an array, so you can play with them individually.
     def secret_garden
       instance_eval "attr_accessor :abra"
@@ -42,7 +42,7 @@ module Gardener
         end
         str << line
       end
-      @abra << str unless str.blank?      
+      @abra << str unless str.blank?
     end
 
     # Take the things that were dumped to a file and put them in the database.
@@ -168,10 +168,9 @@ module Gardener
     {"#{self.class.to_s.underscore}_#{self.id}" => self.attributes}.to_yaml
   end
 
-  # Workaround for DelayedJob which has kind of an unfriendly monkey patch on ActiveRecord::Base
-  # This in itself is kind of rude, since I don't know if anyone besides DelayedJob has a (legitimate) reason
-  # for hanging :yaml_new on AR::Base.  If you notice that my patch to unfuck the DJ patch is fucking you, 
-  # please let me know, I want us all to get along.  Hopefully we'll all get the refinements thing working soon
+  # Workaround for DelayedJob which has an unfriendly monkey patch on ActiveRecord::Base.
+  # If you notice that my patch to unfuck the DJ patch is causing problems please let me know,
+  # I want us all to get along.  Hopefully we'll get refinements working soon :P
   # and stop stepping on each others toes.
   if ActiveRecord::Base.respond_to? :yaml_new
     class ActiveRecord::Base

metadata

@@ -4,9 +4,9 @@ version: !ruby/object:Gem::Version
   prerelease: false
   segments: 
   - 1
-  - 1
-  - 5
-  version: 1.1.5
+  - 2
+  - 0
+  version: 1.2.0
 platform: ruby
 authors: 
 - Bob Larrick
@@ -14,11 +14,16 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-03-14 00:00:00 -04:00
+date: 2011-04-18 00:00:00 -04:00
 default_executable: 
 dependencies: []
 
-description: "A Ruby on Rails Plugin to help you create seed data.  Useful when you want to move a few records from one database or environment to another. "
+description: |-
+  A Ruby on Rails Plugin to help you create seed data.  Useful when you want to move a few records from one database or environment to another. 
+  
+  # staging foo = Model.find(id); foo.plant_seed; 
+  
+  # production Model.reap;
 email: larrick@gmail.com
 executables: []