Blogs of laravel-vapor

As we embarked on the deployment of a Laravel application using Vapor, we encountered an unexpected deviation from the documented process. The network, which was supposed to be automatically created during the initial deployment, failed to materialize. This unforeseen challenge necessitated a manual intervention, requiring us to navigate through the Vapor UI and meticulously configure a new network, specifying both the region and network name. Then we created a fixed publicly accessible database with minimum configuration (db.t3.micro - 2VCPU 1Gib RAM...

Recently I was trying to deploy a Laravel Application using Vapor. I wanted to deploy it to a subdomain. There were many projects deployed on several subdomains of our main domain. Since I wanted to deploy using Vapor which is basically serverless, there were basically no IP Addresses or URLs to point the domain to. I went through the Vapor Documentation about the domain section, but it said nothing about how to point the subdomain. So I contacted the Laravel Vapor support about my problem. They responded that I needed to add the main Domain to Vapor and the subdomain will automatically be added and no problem will happen to my existing subdomains after doing this. After their response, I added the main domain from the Vapor UI. PS: Thanks for the great support from

Laravel Vapor is an auto-scaling, serverless deployment platform for Laravel, powered by AWS Lambda. It is a cost-effective system, you only need to pay for the usage of your application. Vapor makes it easy to use AWS Lambda-powered serverless application in such a way that you don’t need to do any setup for AWS Lambda. Here's a Tutorial on how to deploy a Laravel application with Vapor. The following topics will be covered in this Blog. Setting up Vapor Locally Link AWS Account Creating Projects Deployments