Provide a way to restart after running migrations about dpl HOT 8 CLOSED

Possible solutions:

• add an option for this, don't have a good name, though. restart_after_run? or just restart?

• add special logic to run so you could say

  run:
    - "rake db:migrate"
    - restart

• simply always restart if there are custom commands

from dpl.

Would this work?

run:
  - "rake db:migrate"
  - "heroku ps:restart"

from dpl.

No, first off, these commands are run on a dyno (like heroku run ...), second, the heroku toolbelt is not installed.

from dpl.

I think it would be ideal if Heroku could run migrations as part of the deploy instead of after it. Then only one restart would be required and there'd be nothing to do for this integration.

from dpl.

I think it would be ideal if Heroku could run migrations as part of the deploy instead of after it. Then only one restart would be required and there'd be nothing to do for this integration.

Interestingly, Engine Yard does that.

from dpl.

Heroku used to do this, but that behaviour got changed with the Cedar stack and its focus on being a much more generic application stack.

from dpl.

I guess you could make it part of the buildpack, except you don't have the database connection available during slug compilation.

from dpl.

I guess that explains it. Well, for now, option two makes sense to me:

run:
  - "rake db:migrate"
  - restart

It's pretty obvious when the restart happens.

from dpl.