No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
Creates a directory db/backup in the rails app and creates / loads YML files from there. After a backup, the db/backups directory is archived into a .tgz file and then deleted. When restoring, the db/backup directory is extracted from the .tgz file. All of the files in the 'files' directory are also backed up / restored. The default archive file is "site-backup.tgz" but any other one can be passed as an argument to both db:backup:write and db:backup:read, for example: app1$ rake db:backup:write app1$ cd ../app2 app2$ rake db:backup:read[../app1/site-backup.tgz] The environment variable 'verbose' or 'VERBOSE' if defined will result in some verbose output. To add the rake tasks to your Rails app, simply install the gem, and then add the following line to your 'Rakefile': require 'rails-backup-migrate'
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

 Project Readme

Rails Backup Migrate

A gem that provides a rake task for backing up your database and uploaded files to an archive and restoring them from an archive.

You can archive schema, schema+data, files, or schema+data+files. Each archive action has a restore counterpart. The data from the database is backed up to a .yml file for each table that is database independent.

So you can use Rails Backup Migrate to get data out of one kind of database and easily load it into another kind.

Quick Start

Installing the gem:

  $ gem install rails-backup-migrate

Add the following line to your rails application’s Rakefile

  require 'rails-backup-migrate'

To backup everything in a rails instance:

  $ rake site:backup

Everything is saved in an archive file, named by default ‘site-backup.tgz’. Copy/move this to another rails instance

  $ rake site:restore

More info

The backup file can be specified with a command line argument in rake’s (wierd) format:

  $ rake site:backup[/path/to/file.tgz]

Compatibility

Tested initially on ‘redmine’ using rails 2.3.11 and some simpler tests with rails 3. Has been tested with MySQL and Sqlite3 databases. Further testing with postgres to be done.

Also tested with a dummy rails 3.0 app using sqlite3 driver in ruby 1.8.7, 1.9.2 and jruby 1.6.2.

This requires a system with access to the `tar` command in your path. (Easy for Mac & *nixes, may require a posix environment such as cygwin under Windows.)

Known Issues:

- under ruby 1.9.2, the YAML export (in the `rake site:backup` task fails extended characters in ASCII to UTF8 conversion) (Github Issue #4) Changes made in 0.0.9 that look like this is fixed – any help regressing is welcome!

Contributors

Matt Connolly – main author of gem
Tobias Lütke – wrote a `backup.rake` file that inspired the database backup portion.

License

GPL – See LICENSE