Blog /

Product

Product November 24, 2020

Forge: Streaming Backups & More

Since launching Forge's Database Backup feature [back in February](https://blog.laravel.com/forge-database-backups-now-supported), our customers have created thousands of backup configurations, which have made hundreds of thousands of backups and counting. In June, [we extended the backup providers](https://blog.laravel.com/forge-custom-backup-providers) to support any S3-compatible host, which means you can bring your favorite provider such as MinIO, Linode Objects, Backblaze, and more. Today, we're pleased to announce a big improvement to database backups including **streaming backups directly to your backup provider**. By streaming your database backups to your backup provider, the backup files themselves never consume disk space on your server. Database streaming will only affect newly created backup configurations, and existing configurations will continue to work as they have in the past. If you would like to take advantage of this feature, you may delete and recreate your database backup configuration within the Forge dashboard. Forge is also now able to report on "Partial" backups. A partial backup may occur when you've configured your backup to run on two or more databases, but not all databases were able to be backed up successfully. Partial backups will halt the remainder of the backup process. ![](https://laravel-blog-assets.s3.amazonaws.com/wekernxxs6aROScTZpz7kPYcWLdRXUcwWZ6gwBri.png)To provide these improvements, we had to make some key changes to how backups run, including: - Each database is backed up into its own `.sql.gz` archive, rather than all databases being archived into one file. This results in faster restores as we no longer need to extract the selected database dump first. - We now include the `CREATE DATABASE` and `USE` statements for each database that is backed up. The Forge database backup code is open-source at: [https://github.com/laravel/forge-database-backups](https://github.com/laravel/forge-database-backups) If you don’t have a [Forge](https://forge.laravel.com/) account, now is a great time to sign up! Forge allows you to painlessly create and manage PHP servers which include MySQL, Redis, Memcached, database backups, and everything else you need to run robust, modern Laravel applications.

James Brooks

Product November 20, 2020

Forge: New AWS ARM Instance Types Available

Starting today, you can provision T4g AWS servers using Laravel Forge. These instance types are powered by AWS Graviton2, a processor built by AWS using 64-bit ARM cores. These instance types provide a performance benefit of [up to 40% at a 20% lower cost](https://aws.amazon.com/blogs/aws/new-t4g-instances-burstable-performance-powered-by-aws-graviton2/) in comparison to T3 instances. T4g instances are available in US East (N. Virginia, Ohio), US West (Oregon), Asia Pacific (Tokyo, Mumbai), and Europe (Frankfurt, Ireland). If you don’t have a [Forge](https://forge.laravel.com/) account, now is a great time to sign up! Forge allows you to painlessly create and manage PHP servers which include MySQL, Redis, Memcached, database backups, and everything else you need to run robust, modern Laravel applications.

Mohamed Said

Product November 5, 2020

Forge: Nginx Templates

Today we're excited to introduce a new feature to [Laravel Forge](https://forge.laravel.com) called **Nginx Templates**. These templates allow you to define your own base Nginx configuration files that can be used when creating your sites. You may have found yourself needing to make manual adjustments to a Forge site's Nginx configuration file. If you do this often, Forge's Nginx Templates can save you a lot of time. You can use these templates for anything from making small, common adjustments, to powering completely different types of applications such as those written other frameworks or languages. You may create a template via the "Nginx Templates" tab on your server's management screen: ![](https://laravel-blog-assets.s3.amazonaws.com/70C3WFMpjvt6hkAva6j9Y36mteZ5jofGtBBkUoyy.png)When creating a new site, you will have the option to select any of that server's available templates to use, or you may choose to use Forge's default Nginx template: ![](https://laravel-blog-assets.s3.amazonaws.com/8LP9VHo9PXakfLlGjGXCIy7FU5HvIvJIgUhpdUoP.png)You can read more about Nginx templates and the variables accessible to templates on the [documentation page](https://forge.laravel.com/docs/1.0/servers/nginx-templates.html). Nginx templates are available to all Forge plans. We hope that you enjoy this new feature! If you don’t have a [Forge](https://forge.laravel.com) account, now is a great time to sign up. Forge allows you to painlessly create and manage PHP servers which include MySQL, Redis, Memcached, database backups, and everything else you need to run robust, modern Laravel applications.

James Brooks

Product November 4, 2020

Introducing The Envoyer API

Today we're excited to release our API for [Envoyer](https://envoyer.io)! You can create new API tokens from your Envoyer [account page](https://envoyer.io/user/profile#/api). Each token can be scoped to provide limited access to your data. ![](https://laravel-blog-assets.s3.amazonaws.com/A6bydDSK9OZWJUwQfeJqnLsDzu39GKcxDqo6ymxO.png)We're excited to continue improving the API and seeing what you build. Please give us your feedback! You can learn more about the Envoyer API by reading our official [documentation](https://envoyer.io/api-documentation).

James Brooks

Product October 26, 2020

Forge: Upgrading To Composer 2.0

Following the release of Composer 2 on October 24th, we wanted to share a guide on how to upgrade your servers to make the most of all the great benefits it brings. First, all new servers will automatically receive Composer 2 by default. For existing servers, you should **delete and recreate** (if desired) the scheduled job within your Forge dashboard that updates your Composer installation every week. By default, Forge created this job with the` --1` flag, which instructs Composer to not upgrade to 2.0. After you have deleted the scheduled task, you may recreate it without the `--1` flag. Next, you have two options: 1. SSH into each of your servers and manually upgrade Composer. 2. Create a recipe and run it against each of your servers. For those of you with just a few servers, connecting to the server and manually running the upgrade command is likely sufficient; however, if you have multiple servers that need upgrading, you can save yourself time by creating a recipe. To upgrade, the following command should be executed: ``` composer self-update --2 ``` This will instruct Composer to update itself and specifically select version 2. And that’s it, we’re done! If your application is not compatible with Composer 2, you can roll back to Composer 1 at any time: ``` composer self-update --1 ``` ---

James Brooks

Product October 20, 2020

Forge: Enabling TLS 1.3

As of today, newly issued LetsEncrypt certificates on Laravel Forge servers that run on Ubuntu 20.04 have TLS 1.3 enabled by default. TLS 1.3 offers a faster handshake and more secure cipher suites. If you have an existing LetsEncrypt certificate, you will need to issue a new one and activate it in order to receive the upgrade to TLS 1.3.

Mohamed Said

Showing 111 - 120 of 172 results

Stay connected with the latest Laravel news