Leveling up Laravel deployments: Unlocking optionality

This is how I like to do deployments for Laravel applications. This involves using a CI pipeline, instead of (blindly) deploying based on git webhooks. There’s a lot of reasons why deployments can get bogged down and, frankly, suck. Let’s see how to get unstuck by adding some process to our deployments. The two main things that buy you optionality are: 1. An approval process 2. A deployable build artifact These gives you lots of options! You can prevent bad code from going to production with an enforced approval process. When a build artifact, you can run your code from different points in time (without having to worry about nodejs dependency issues), test out other platforms, build containers, and run all sorts of experiments with little hassle. Check out the same repository: ⌚️ Timestamps 00:00 Deployments: Complicated! 00:35 Why optionality? 01:30 You need a CI pipeline 01:54 GitHub Action setup (approval) 04:18 Build a deployable artifact 06:35 Need your feedback