dumper 1.1.0 → 1.1.1

data/README.md

@@ -1,12 +1,10 @@
 # Dumper Agent for Rails
 
-Dumper is a backup management system that offers a whole new way to take daily backups of your databases.
-
-**This app will be launched soon!**
+[Dumper](http://dumper.io/) is a backup management system that offers a whole new way to perform automated backups of your databases.
 
 ## Supported Stacks
 
-* Ruby 1.8.7 , Ruby 1.9.2 or later
+* Ruby 1.8.7, Ruby 1.9.2 or later
 * Rails 3.0 or later
 * MySQL with ActiveRecord
 * PostgreSQL with ActiveRecord
@@ -22,7 +20,7 @@ Add the following line to your Rails project Gemfile:
 gem 'dumper'
 ```
 
-then create `config/initializers/dumper.rb` and put the following line.
+then create `config/initializers/dumper.rb` and add the following line:
 
 ```ruby
 Dumper::Agent.start(:app_key => 'YOUR_APP_KEY')
@@ -36,11 +34,11 @@ You'll find your application is registered and ready to take backups.
 
 ## How does it work?
 
-In a Rails app server process, a new thread is created and periodically checks the Dumper API if a new backup job is scheduled.
+In a Rails app server process, a new thread is created and periodically checks the Dumper API to see if a new backup job is scheduled.
 
-When it finds a job, the agent won't run the job inside its own thread, but instead spawns a new process, then go back to sleep. That way, web requests won't be affected by the long-running backup task, and the task will continue to run even when the parent process is killed in the middle.
+When it finds a job, the agent won't run the job inside its own thread, but instead spawns a new process, then goes back to sleep. That way, web requests won't be affected by the long-running backup task, and the task will continue to run even when the parent process is killed in the middle.
 
-Dumper agent will try to run on every process by default. Which means, for instance, if you have 10 thin instances on production, the agent will run on those 10 instances. We designate the first agent that hits our API as primary, and the rest as secondary. In this case, 1 thin process becomes the primary and other 9 processes become secondaries. Only the primary is responsible for taking backup jobs, so it is guaranteed that there is no duplicate work on your servers. The primary polls our API with up to 1- to 10-minute interval, while the secondaries poll every hour. If you run fork-based servers like unicorn or passenger, however, the agent thread runs only on the master process, not on child processes.
+Dumper agent will try to run on every process by default. Which means, for instance, if you have 10 thin instances on production, the agent will run on those 10 instances. We designate the first agent that hits our API as primary, and the rest as secondary. In this case, 1 thin process becomes the primary and other 9 processes become secondaries. Only the primary is responsible for taking backup jobs, so it is guaranteed that there is no duplicate work on your servers. The primary polls our API with every 1- to 10-minute interval, while the secondaries poll every hour. If you run fork-based servers like unicorn or passenger, however, the agent thread runs only on the master process, not on child processes.
 
 We do this for fault tolerance. When something goes wrong and the primary dies, one of the secondaries will take over the primary status and continue to serve.
 
@@ -50,7 +48,7 @@ The bottom line is that the agent is designed to be extremely efficient in CPU,
 
 As explained above, the Dumper agent will try to run on every process by default.
 
-If you want to start the agent on a particular host, pass a block that evaluates to true or false to `start_if` method.
+If you want to start the agent on a particular host, pass a block that evaluates to true or false to the `start_if` method.
 
 ```ruby
 Dumper::Agent.start_if(:app_key => 'YOUR_APP_KEY') do
@@ -58,7 +56,7 @@ Dumper::Agent.start_if(:app_key => 'YOUR_APP_KEY') do
 end
 ```
 
-In particular, current Redis support is limited in that you must run the agent on the same host with Redis.
+Currently Redis support is limited in that you must run the agent on the same host with Redis.
 
 ```ruby
 Dumper::Agent.start_if(:app_key => 'YOUR_APP_KEY') do

data/lib/dumper/stack.rb

@@ -23,6 +23,11 @@ module Dumper
         @rails_env = Rails.env.to_s
         @rails_version = Rails::VERSION::STRING
         @is_supported_rails_version = (::Rails::VERSION::MAJOR >= 3)
+
+        if defined?(MongoMapper)
+          MongoMapper.database # Creates the Mongo::DB instance
+        end
+
         DATABASES.each do |key, klass|
           database = klass.new
           next unless database.set_config_for(@rails_env) || database.set_config_for(options[:additional_env])

data/lib/dumper/version.rb

@@ -1,3 +1,3 @@
 module Dumper
-  VERSION = '1.1.0'
+  VERSION = '1.1.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dumper
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-06-24 00:00:00.000000000 Z
+date: 2012-06-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: multi_json