When putting your application in maintenance mode using the `vapor down` command, your application will respond with a status code of 503 on every request. Beginning today, you may use the `secret` option on the `vapor down` command to specify a maintenance mode bypass token:...
Starting today, you can now serve assets from the root domain. To get started, just head over to your application's `config/vapor.php` file, and add an array of assets that should be served
Starting today, you can now disable Vapor updates on the laravel-vapor-role role and manage this role yourself in AWS Console. To disable updates on the laravel-vapor-role role, just head over to...
Today we are launching an exciting new feature for Vapor UI Dashboard: Job Metrics. The "Job Metrics" tab allows you to monitor in real-time...
Today on Vapor, we're proud to introduce you to our new open-source package: Vapor UI. In short, this package provides a beautiful dashboard through your application that allows you to monitor your application's logs...
Amazon just announced that API Gateway 2.0 now supports wildcard custom domain names. With this new feature, you can now combine a wildcard domain...
Today we released version v1.7.0 of `laravel/vapor-cli`. This release includes a new `tinker` command. Using the new command, you can execute code on Vapor using Laravel Tinker.
Starting today, you can add Imagick support to your projects by importing an external Lambda layer. This change decreases the size of the default Vapor runtime layer and allows customers that don't use Imagick to upload larger applications without worrying about AWS Lambda application size...
When you launch an application on Laravel Vapor, we use AWS API Gateway to point web traffic to the AWS Lambda function that is powering your application. Normally, this is all magic that happens behind the scenes when using Vapor.A few months ago, Amazon released...
Today we released laravel/vapor-core version v2.5.1 with the ability to handle custom Lambda events. To get started, implement a vapor:handle artisan command in your application with the following signature:vapor:handle {payload}To extract the event payload from the payload argument, you should base64_decode and json_decode the string:
On February 10th, we've released v2.4.1 of laravel/vapor-core. This release includes an important fix for long running queued jobs. Before this fix, long running jobs were left to be terminated by Lambda after reaching the timeout set by queue-timeout in your vapor.yml file....
Starting today, new Vapor deployments will ensure a separate AWS Lambda function exists for running your queued jobs.Before this change, queued jobs executed within the CLI Lambda. This Lambda is also used for running deployment commands, CLI commands, and scheduled jobs. However, there were potential...