Many people pair the convenient server provisioning of Forge with the zero-downtime deployment magic provided by Envoyer. Previously, when adding Forge servers to your Envoyer project, you needed to copy over the server name, IP address, deployment path, PHP version, and more. …
Last week we tagged version 8.0.0 of Laravel Cashier. This release should not contain any breaking changes from the 7.0 series of Cashier; however, thanks to a community contribution, the release does add automatic support for more Stripe webhooks.
The following webhooks are now automatically handled by Cashier unless you…
As you may know, Forge allows you to upgrade to new major releases of PHP. However, beginning today, you can upgrade to the latest patch release of PHP within your current major version. For example, if your server is currently running on PHP 7.2.2, you can upgrade to PHP 7.2.11 (or whatever the latest patch release happens to be).
You can upgrade your server’s PHP version on the “PHP” tab of the server’s management panel. Note that any PHP upgrade can cause downtime on your server — so take special care when performing these operations on production servers!
If you don’t have a Forge account, now is a great time to sign up. Forge allows you to painlessly create and manage PHP 7.2 servers which include MySQL, Redis, Memcached, and everything else you need to run robust, modern Laravel applications.
Laravel’s first employee, Mohamed Said, joined the team over two years ago. Last month we added our second employee: Dries Vints. Dries has been a part of the Laravel community for a very long time — as long as I can remember.
Beginning today, Forge now allows you to select the subnet that AWS servers should be place in when provisioning. This feature gives you more control over the network configuration of your Forge AWS servers. Previously, all AWS servers were placed in a “Laravel Forge” VPC with a default subnet that was configurable:
Creating New VPCs
In addition, Forge also now allows you to create additional new VPCs when creating your servers. To create a new VPC, select the “Create New” option in the “VPC” drop-down selection menu and enter the desired name for your VPC:
Beginning tomorrow, Forge will begin using Bitbucket’s 2.0 API by default, since the 1.0 API will be removed from service at the end of this year.
Bitbucket’s 2.0 API does not have feature parity with their old API; therefore, after creating new servers, you will need to manually add the server’s SSH key to your Bitbucket account.
Unfortunately, Bitbucket does not allow adding SSH keys to a user’s account using an OAuth2 access token — they may only be added using the password, “apppassword”, and session authentication methods. When installing a Bitbucket repository onto your Forge server, Forge will display the SSH key that you will need to add to your Bitbucket account:
We’re sorry for the inconvenience this causes and hope that Bitbucket will allow adding SSH keys to a user’s account via OAuth tokens in the future.
I’m thrilled to announce the newest member of the Laravel ecosystem: Laravel Nova. Nova is a beautifully designed administration panel for Laravel. We’ve sweat the small details and carefully crafted Nova to not only look great, but to be a joy to work with.
Today we are launching support for custom SSH ports on Forge. Previously, all SSH traffic from Forge used the default port 22. Beginning today, you are able to customize this port when creating a Custom VPS:
In addition, using the server’s “Meta” tab, you may adjust the SSH port for existing custom VPS servers as well as existing first-party servers on DigitalOcean, Linode, AWS, and Vultr: