Hookup takes care of Rails tedium like bundling and migrating through Git hooks. It fires after events like
- pulling in upstream changes
- switching branches
- stepping through a bisect
- conflict in schema
gem install hookup cd yourproject hookup install
Each time your current HEAD changes, hookup checks to see if your
Gemfile.lock, or gem spec has changed. If so, it runs
bundle check, and if that indicates any dependencies are unsatisfied,
Each time your current HEAD changes, hookup checks to see if any
migrations have been added, deleted, or modified. Deleted and modified
migrations are given the
rake db:migrate:down treatment, then
db:migrate is invoked to bring everything else up to date.
Hookup provides a
-C option to change to a specified directory prior to
rake. This should be used if your
Rakefile are in a non-standard location.
To use a non-standard
db directory (where
--schema-dir="database/path" to the
To force reloading the database if migrating fails, add
--load-schema="rake db:reset" to the
hookup post-checkout line in
Each time there's a conflict in
db/schema.rb on the
Rails::Schema.define line, hookup resolves it in favor of the newer of
the two versions.
Copyright (c) Tim Pope. MIT License.