Hacker News Reader

Parent Full thread

tomschlick

Laravel already has multiple ways to deploy (other than rolling your own):

Laravel Forge - Deploys a VPS on your own AWS/DigitalOcean/Hetzner/etc - https://forge.laravel.com/

Laravel Vapor - Deploys a serverless function on your AWS account to run your app/cron/queues https://vapor.laravel.com

Laravel Cloud - Differs because it doesn't run on your infrastructure, so less time to setup/configure.

View on HN

Maybe it makes sense from this angle:

Laravel forge - something breaks, you are responsible to fix it

Laravel vapor - something breaks, you are responsible to fix it

Laravel Cloud - something breaks and you can prove, that it's not you code? Someone else is responsible, awesome!

Most projects that use laravel are small shops. To sell them the convenience that they don't need to bother about infrastructure and uptime, is a smart move by laravel.

And envoyer

Reply on news.ycombinator.com