Skip to content
Resets (and if available, seeds) your databases.
Ruby
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
lib Bump version to 0.0.10 Dec 11, 2013
.gitignore Initial commit Jul 16, 2012
Gemfile Initial commit Jul 16, 2012
README.md README wording tweak Jul 16, 2012
Rakefile Initial commit Jul 16, 2012
app_reset.gemspec Removed awesome_print as a dependency Sep 5, 2012

README.md

AppReset

Why?

Compared to db:reset:

db:reset resets your database from schema.rb - during early stage of development, the migration files are often edited directly to keep the sanity.

Compared to db:migrate:reset:

AppReset always calls db:create to ensure databases exist, and then calls db:migrate:reset. It also ensures seeds.rb will get called if you are in a rails engine environment.

AppReset basically replaces the following steps:

  • db:create
  • db:migrate:reset
  • RAILS_ENV=test db:migrate:reset
  • run seeds.rb from your rails engine

Installation

It is recommended you only include app_reset in your development environment:

gem 'app_reset', :group => :development

If you are using it in a rails engine, don't forget to require it:

require 'app_reset' if Rails.env.development?

Usage

Resets (and if available, seeds) your development and test databases via:

rake app:reset

License

This gem is released under the MIT License.

Author

Fred Wu

Something went wrong with that request. Please try again.