Ep. 2: Over-engineering migrations even more!
In the second episode of the podcast we talk with Tim MacDonald [https://phpc.social/@timacdonald] 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 [https://twitter.com/MaybeEdward/status/1625936404558581766?s=20]
* Lukas Heller's mention of the "path" option in artisan migrations [https://mas.to/@lph/109870633435661093#]
* Brendan White's blog post on Data Changes in Laravel [https://brendancodes.wordpress.com/2023/02/24/data-changes-in-laravel/]
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:
