Skip to main content

Vapor Amazon Linux 2 Runtimes Are Now Available in laravel8

The runtime configuration option in the vapor.yml allows you to specify which PHP version a given environment uses. Amazon recently announced the second version of its operating system: Amazon Linux 2 - that provides optimized performance and long term support, without any additional charges. Starting today, you may start using PHP on top of Amazon Linux 2 by updating the runtime configuration option in the vapor.yml like so: id: 3 name: vapor-app environments: production: - runtime: php-8.0 + runtime: php-8.0:al2 Once the environment is deployed, your application will automatically start using Amazon Linux 2 with zero downtime. Keep in mind that using Amazon Linux 2 is highly recommended, as Amazon Linux 1 will end-of-life its standard support on December 31, 2020. After that date, Amazon will only be making "maintenance support" updates to the operating system. We hope you enjoy this new addition to Laravel Vapor. At Laravel, we're committed to providing you with the most robust and developer-friendly PHP experience in the world. If you haven't checked out Vapor, now is a great time to start! You can create your account today at: vapor.laravel.com.

Popular posts from this blog

Create Your Next Project's Readme in Laravel8 | laravelnote

  The readme.so editor gives you visual cues, starter section templates and includes many standard readme sections you're likely to use. It also has a nice preview to help guide you along the way. Never forget a section for your readme again! Select sections to add to your readme, edit the contents, and drag to rearrange. See a live-updating rendered preview of your markdown, then download your README.md file! Here's an example of starting an API section, which provides helpful formatting. You might need to specify API params: The editor includes both light and dark editor support, and you can download or copy/paste the raw markdown of your readme into version control once you're done. You can learn more about this project and start using it on  readme.so . Also, be sure to check out  readme.so on Product Hunt  and upvote it if you find it useful!

Octane Support in Laravel forge 2021 5 may

 Back in March, Taylor announced the new Laravel Octane project at Laracon Online. Since then, we've been busy working on bug fixes and enhancements to Octane, as well as adding support to Laravel Forge. Today we're pleased to announce that Octane support is available in Forge. We've written the guide below to help you get started. Please keep in mind that Octane is still in beta and should not be used in production. Prerequisites Your project must require "laravel/octane": "^0.3.2" or above. Your server must have PHP 8.0 installed. You should then follow the Octane installation instructions listed in the Octane repository. Creating an Octane Site Octane can be enabled by selecting the Laravel Octane (Beta) project type option and PHP 8.0 as the PHP version that should be used to serve your site: Laravel Octane Project Type Laravel Octane Project Type Once the project type has been selected, Forge will ask for the port that Octane should listen on. Unlik...

Check if a Laravel request is from the CLI on Laravelnote

  There might be times where you need to know if a request to your Laravel app is coming from the CLI or from the web. As an example, I wanted to turn on the   query log   to dump out all the SQL queries. In AppServiceProvider I added a simple config check to turn on the the log: if (config('settings.profile')) { \DB::connection()->enableQueryLog(); } With this in place, it would run for web requests, as I wanted, but the side effect is it would also be turned on in our queue jobs and other CLI tasks. Laravel runningInConsole | Laravelnote Laravel provides a simple helper called  runningInConsole  that you can use to help determine what environment you are in. app()->runningInConsole() With this I could just an inverse check to make sure my code only runs when it's a web request: if (config('settings.profile') && ! app()->runningInConsole()) { \DB::connection()->enableQueryLog(); } If you ever come to a situation where you need to know w...