In the second episode of the podcast we talk with Tim MacDonald about a few other approaches to how you might manage other operations that happen before/during/after a database migration (or really any deploy step). Tim pitches a lower-level approach that spawns a whole new line of thinking.

We also touch on some of the responses to episode one, including:

• Ed Grosvenor's "run once" command
• Lukas Heller's mention of the "path" option in artisan migrations
• Brendan White's blog post on Data Changes in Laravel