I am using Rails 3.2.13.
The engine is adding itself to the Rails path like this:
initializer "fort.load_app_instance_data" do |app|
app.config.paths['db/migrate'] += Fort::Engine.paths['db/migrate'].existent
The whole file can be viewed here.
I have a bunch of migrations in the base Rails app (located in db/migrate) and then a couple migrations inside of an engine (located in engines/<engine>/db/migrate).
resulting in all the migrations being listed as up when I check the status (rake db:migrate:status). This is the desired result.
The same thing does not occur when I check the status after running rake db:migrate:reset. The migrations located in the engines migrate directory are still listed as down.
The full output can be viewed in this gist.
katello-reset-dbs - db:migrate:reset is acting unexpectedly
It seems that db:migrate:reset is ignoring migrations located in our
engines. I filed a bug against rails  to hopefully get it fixed.
This issue has been automatically marked as stale because it has not been commented on for at least
The resources of the Rails team are limited, and so we are asking for your help.
If you can still reproduce this error on the 4-1-stable, 4-0-stable branches or on master,
please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.
This issue has been automatically closed because of inactivity.