Douglas Lovell

In the way-back machine, Capistrano had a "deploy:cold". In Capistrano 3.10.1, `bundle exec cap staging deploy:updating` gives me enough to shell-in and run the `db:structure:load` or `db:schema:load` task manually. Shelling...

Edit: I definitely wouldn't like every deploy to consider wiping the database and then skip it ~based on a semaphor file~. That feels way too dangerous to me.

> With `db:schema:load` some required extensions described in migrations wasn't enabled in the new database. Don't describe required extensions in migrations?

Ouch. Pardon me. It really was a question. It probably sounded a little glib. Excuse me. And also this is a little orthoganal to the thread. Maybe we should take...

Based on a few samples, I've found 100% correlation between the occasions on which delayed_job needed to be restarted and dates on which MySQL was restarted. And by way of...