Shipping to Production

A feature isn’t shipped until it’s live, and “live” means someone, possibly you, is now responsible for it staying up, staying patched, and surviving the traffic it gets. This chapter isn’t about writing more code; it’s about the last mile between “works locally” and “a real client is using this.”

• Laravel: Forge and Vapor ($) covers Laravel’s own official deployment products.
• Cloud Hosting: AWS, GCP, and Azure the Pragmatic Way covers deploying when the client already has a cloud contract.
• Platform.sh ($): One Deploy Story for Several Frameworks covers a managed PaaS that isn’t tied to one framework.
• WordPress: Managed Hosting Done Right (Kinsta, WP Engine $) covers hosting built specifically around WordPress’s needs.
• Nextcloud: All-in-One Docker Deployment covers the officially recommended, self-hosted deployment path.