Product

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: 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: 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.

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. 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).

Over the last few days, we've been working on some enhancements on Vapor. Starting today, you can now quickly debug failing deployment hooks directly from the console.

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.

Forge has always supported using a custom Git provider for your projects, but starting today Forge has first-party support for self-hosted GitLab installations. This means that Forge now provides a better integration for your self-hosted GitLab repositories: - Validation that the repository and branch exists - Automatically adds the server key to the repository so that it can be cloned You can connect your self-hosted GitLab installation in your account page, [https://forge.laravel.com/user/profile#/source-control](https://forge.laravel.com/user/profile#/source-control) We hope that you enjoy this new feature.

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: ``` vapor down --secret=1630542a-246b-4b66-afa1-dd72a4c43515 ``` You may then navigate to the application URL matching this token and Vapor will issue a maintenance mode bypass cookie to your browser: ``` https://example.com/1630542a-246b-4b66-afa1-dd72a4c43515 ``` After accessing this hidden route, you will then be redirected to the `/` route of the application. Once the cookie has been issued to your browser, you will be able to browse the application normally as if it was not in maintenance mode. To use this feature, you need to make sure your application is using these versions: - `laravel/framework` v8.0+ - `laravel/vapor-core` v2.9.3+ - `laravel/vapor-cli` v1.9.4+