Sha256: 2ea1da2e4d6a695968394015b78a19ac77d4d46dc1a8e332ccbf7da188005e10
Contents?: true
Size: 1.53 KB
Versions: 2
Compression:
Stored size: 1.53 KB
Contents
# capistrano-mongo-sync Use capistrano-mongo-sync to sync your local development database from your production database using: ```ruby cap production mongo:pull ``` Or sync just one collection from the database: ```ruby COLLECTION=users cap production mongo:pull ``` Or sync some records (comma separated list of mongo id's) from one collection from the database: ```ruby COLLECTION=users IDS=1,2,3,4 cap production mongo:pull ``` Or sync your staging database from your production database. ```ruby cap production mongo:sync_prod_to_staging ``` If you've already downloaded a mongo dump with the cap task, it will ask you if you'd like to use that local dump. If someone has already created a mongo dump recently on the remote server, the cap task will ask if you'd like to use that dump. Older mongodumps, both remote and local, will be deleted when you run the cap task. ## Usage Add to your Gemfile: ```ruby gem 'capistrano-mongo-sync' ``` Require in `Capfile` to use the predefined tasks: ```ruby require 'capistrano/mongo-sync' ``` In deploy.rb, set some variables: ```ruby set :production_db, 'PRODUCTION_DB' set :development_db, 'DEVELOPMENT_DB' ``` set some optional variables: ```ruby set :staging_db, 'STAGING_DB' ``` enable hipchat notifications (requires hipchat gem): ```ruby set :hipchat_client, HipChat::Client.new('HIPCHAT_TOKEN') ``` change where mongodumps are kept remotely and locally: ```ruby set :remote_dump_base, '/tmp/dumps' set :local_dump_base, '/tmp/dumps' ``` Or write your own tasks using the MongoSync class
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
capistrano-mongo-sync-0.1.7 | README.md |
capistrano-mongo-sync-0.1.6 | README.md |