jtrupiano-sanitize_email 0.1.0 → 0.1.1

data/README.rdoc

@@ -0,0 +1,107 @@
+= sanitize_email
+
+This gem allows you to globally override your mail delivery settings.  It's particularly helpful when you want to omit the delivery of email (e.g. in development/test environments) or alter the to/cc/bcc (e.g. in staging or demo environments) of all email generated from your application.
+
+It is a "configure it and forget it" type gem that requires very little setup.  It includes some very innocuous monkey patching of ActionMailer::Base to work its magic.
+
+Peter Boling wrote the plugin that this gem is derived from.  It currently solves three common problems in ruby web applications that use ActionMailer:
+
+=== Working Locally with Production Data
+
+Peter described this common problem in his original plugin implementation as such:
+
+* I have a production site with live data.
+* I dump the live data and securely transfer it to another machine (rync -e ssh), and import it using scripts that I will soon open source to.
+* On this separate machine (staging, or development) I run tests, and test various features.
+* I usually want the emails to get sent from these non-production environments so I can verify what they look like when sent, but I don't ever want to risk them getting sent to addresses that are not mine.
+
+=== Re-routing Email on a Staging or QA Server
+
+Another very important use case for me is to transparently re-route email generated from a staging or QA server to an appropriate person.  For example, it's common for us to set up a staging server for a client to use to view our progress and test out new features.  It's important for any email that is generated from our web application be delivered to the client's inbox so that they can review the content and ensure that it's acceptable.  Similarly, we set up QA instances for our own QA team and we use {rails-caddy}[http://github.com/jtrupiano/rails-caddy] to allow each QA person to configure it specifically for them.
+
+=== Testing Email from a Hot Production Server
+
+If you install this gem on a production server (which I don't always do), you can load up script/console and override the to/cc/bcc on all emails for the duration of your console session.  This allows you to poke and prod a live production instance, and route all email to your own inbox for inspection.  The best part is that this can all be accomplished without changing a single line of your application code.
+
+== Install
+
+    gem sources -a http://gems.github.com/
+    gem install jtrupiano-sanitize_email
+
+== Setup
+
+It only requires a few lines of configuration:
+
+* Rails 1.x: Add to bottom of environment.rb
+		
+* Rails 2.x: Use an initializer, stick it in any initializer file, or create a new one for sanitize_email
+		
+Add this bit and customize for your app:
+
+    # Settings for sanitize_email gem.  These can be overridden in individual config/%env%/environment.rb files.
+
+    require 'sanitize_email'
+    ActionMailer::Base.sanitized_recipients = "jtrupiano@gmail.com"
+    ActionMailer::Base.sanitized_bcc = nil
+    ActionMailer::Base.sanitized_cc = nil
+
+    # These are the environments whose outgoing email BCC, CC and recipients fields will be overridden!  
+    # All environments not listed will be treated as normal.
+    ActionMailer::Base.local_environments = %w( development test staging )
+
+Keep in mind, this is ruby (and possibly rails), so you can add conditionals or utilize different environment.rb files to customize these settings on a per-environment basis.
+
+But wait there's more:
+
+Let's say you have a method in your model that you can call to test the signup email.
+You want to be able to test sending it to any user at any time... but you don't want
+the user to ACTUALLY get the email, even in production. A dilemma, yes?  Not anymore!
+
+All your mailers get a force_sanitize class method which takes precedence over the environment override.
+
+When force_sanitize is nil it will not be used by sanitize_email to determine if it should override the recipients, bcc, and cc.
+
+
+== Example
+
+So here's how you can use force_sanitize to override the override.
+
+Even if you set:
+
+  ActionMailer::Base.local_environments = %w( development )
+
+and are in the development environment, you can override the override anywhere in your code.
+
+    class User < ActiveRecord::Base
+      def test_signup_email_me_only
+        UserMailer.force_sanitize = true
+        UserMailer.deliver_signup_notification(self)
+        UserMailer.force_sanitize = nil
+      end
+
+      def test_signup_email_user_only
+        UserMailer.force_sanitize = false
+        UserMailer.deliver_signup_notification(self)
+        UserMailer.force_sanitize = nil
+      end
+
+      # this third method would conditionally use the overridden recipients based on current Rails environment
+      def test_signup_email_environment
+        UserMailer.deliver_signup_notification(self)
+      end
+    end
+
+Load the console with ruby script/console and regardless of what environment you are in:
+
+	  > User.find(4).test_signup_email_me_only
+	
+and the email will have it's recipients, bcc, and cc overridden to be whatever you set the sanitized values to be.
+Then if you want to send it to the actual user, instead of yourself
+
+	  > User.find(4).test_signup_email_user_only
+
+That's it!  Enjoy!
+
+Copyright (c) 2009 {John Trupiano}[http://smartlogicsolutions.com/wiki/John_Trupiano] of {SmartLogic Solutions, LLC}[http://www.smartlogicsolutions.com]
+Copyright (c) 2008 {Peter H. Boling}[http://www.peterboling.com/about.html] of {9thBit LLC}[http://www.peterboling.com/]
+Released under the MIT license

data/VERSION.yml

@@ -1,4 +1,4 @@
 --- 
 :major: 0
 :minor: 1
-:patch: 0
+:patch: 1

data/lib/sanitize_email/sanitize_email.rb

@@ -37,7 +37,7 @@ module NinthBit
 
         def recipients(*addresses)
           real_recipients *addresses
-          puts "santize_email error: sanitized_recipients is not set" if self.class.sanitized_recipients.nil?
+          puts "sanitize_email error: sanitized_recipients is not set" if self.class.sanitized_recipients.nil?
           localish? ? self.class.sanitized_recipients : real_recipients
         end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: jtrupiano-sanitize_email
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors: 
 - John Trupiano
@@ -10,7 +10,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-03-02 00:00:00 -08:00
+date: 2009-04-25 00:00:00 -07:00
 default_executable: 
 dependencies: []
 
@@ -20,10 +20,10 @@ executables: []
 
 extensions: []
 
-extra_rdoc_files: []
-
+extra_rdoc_files: 
+- README.rdoc
 files: 
-- README.textile
+- README.rdoc
 - VERSION.yml
 - lib/sanitize_email
 - lib/sanitize_email/custom_environments.rb
@@ -53,10 +53,10 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   version: 
 requirements: []
 
-rubyforge_project: 
+rubyforge_project: johntrupiano
 rubygems_version: 1.2.0
 signing_key: 
 specification_version: 2
-summary: "Gemified fork of pboling's sanitize_email plugin: allows you to play with your application's email abilities without worrying that emails will get sent to actual live addresses."
+summary: Tool to aid in development, testing, qa, and production troubleshooting of email issues without worrying that emails will get sent to actual live addresses.
 test_files: []
 

data/README.textile

@@ -1,102 +0,0 @@
-h1. sanitize_email
-
-This gem allows you to quickly globally override your mail delivery settings in depending on the environment.  It's particularly helpful when you want to omit the delivery of email (e.g. in development/test environments) or alter the to/cc/bcc (e.g. in staging or demo environments) of all email generated from your application.
-
-This is the problem I have with site after site:
-
-# I have a production site with live data.
-# I dump the live data and securely transfer it to another machine (rync -e ssh), and import it using scripts that I will soon open source to.
-# On this separate machine (staging, or development) I run tests, and test various features.
-# I usually want the emails to get sent from these non-production evnironments so I can verify what they look like when sent, but I don't ever want to risk them getting sent to addresses that are not mine.
-	
-So Peter Boling wrote a plugin!  And I've taken it and turned it into a gem!
-
-It is an "configure it and forget it" type gem that requires very little setup.  It includes some very innocuous monkey patching of ActiveRecord::Base to work its magic.
-
-
-h2. Install
-
-  gem sources -a http://gems.github.com/
-  gem install jtrupiano-sanitize_email
-
-h2. Setup
-
-It only requires a few lines of configuration:
-
-* Rails 1.x: Add to bottom of environment.rb
-		
-* Rails 2.x: Use an initializer, stick it in any initializer file, or create a new one for sanitize_email
-		
-Add this bit and customize for your app:
-
-<pre>
-  # Settings for sanitize_email gem.  These can be overridden in individual config/%env%/environment.rb files.
-
-  require 'sanitize_email'
-  ActionMailer::Base.sanitized_recipients = "jtrupiano@gmail.com"
-  ActionMailer::Base.sanitized_bcc = nil
-  ActionMailer::Base.sanitized_cc = nil
-
-  # These are the environments whose outgoing email BCC, CC and recipients fields will be overridden!  
-  # All environments not listed will be treated as normal.
-  ActionMailer::Base.local_environments = %w( development test staging )
-</pre>
-
-Keep in mind, this is ruby (and possibly rails), so you can add conditionals or utilize different environment.rb files to customize these settings on a per-environment basis.
-
-But wait there's more:
-
-Let's say you have a method in your model that you can call to test the signup email.
-You want to be able to test sending it to any user at any time... but you don't want
-the user to ACTUALLY get the email, even in production. A dilemma, yes?  Not anymore!
-
-All your mailers get a force_sanitize class method which takes precedence over the environment override.
-
-When force_sanitize is nil it will not be used by sanitize_email to determine if it should override the recipients, bcc, and cc.
-
-
-h2. Example
-
-So here's how you can use force_sanitize to override the override.
-
-Even if you set:
-
-  ActionMailer::Base.local_environments = %w( development )
-
-and are in the development environment, you can override the override anywhere in your code.
-
-<pre>
-  class User < ActiveRecord::Base
-    def test_signup_email_me_only
-      UserMailer.force_sanitize = true
-      UserMailer.deliver_signup_notification(self)
-      UserMailer.force_sanitize = nil
-    end
-
-    def test_signup_email_user_only
-      UserMailer.force_sanitize = false
-      UserMailer.deliver_signup_notification(self)
-      UserMailer.force_sanitize = nil
-    end
-
-    # this third method would conditionally use the overridden recipients based on current Rails environment
-    def test_signup_email_environment
-      UserMailer.deliver_signup_notification(self)
-    end
-
-  end
-</pre>
-
-Load the console with ruby script/console and regardless of what environment you are in:
-
-	> User.find(4).test_signup_email_me_only
-	
-and the email will have it's recipients, bcc, and cc overridden to be whatever you set the sanitized values to be.
-Then if you want to send it to the actual user, instead of yourself
-
-	> User.find(4).test_signup_email_user_only
-
-That's it!  Enjoy!
-
-Copyright (c) 2008 Peter H. Boling of 9thBit LLC
-Released under the MIT license