Product

Next.js is a React framework developed by [Vercel](https://vercel.com). It includes functionality such as server-side rendering and static site generation. Today we’ll explain how you can deploy your Next.js application with [Laravel Forge](https://forge.laravel.com). If you’re following along with your own Forge server, ensure that the server is a “App” or “Web” server so that Nginx is installed. In this post, we’ll explain how to deploy your site using the Next.js server-side rendering feature. ## Creating An Nginx Template To use server-side rendering, we first need to create a new [Nginx Template](https://forge.laravel.com/docs/1.0/servers/nginx-templates.html) in Forge. We’re using an Nginx Template here so that we don’t need to modify our site’s Nginx configuration later. We’ll create a new template with a name of “Next.js App” and then update the contents of our template: ```nginx # FORGE CONFIG (DO NOT REMOVE!) include forge-conf/{{ SITE }}/before/*; server { listen {{ PORT }}; listen {{ PORT_V6 }}; server_name {{ DOMAINS }}; server_tokens off; root {{ PATH }}; # FORGE SSL (DO NOT REMOVE!) # ssl_certificate; # ssl_certificate_key; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Content-Type-Options "nosniff"; index index.html index.htm; charset utf-8; # FORGE CONFIG (DO NOT REMOVE!) include forge-conf/{{ SITE }}/server/*; location / { proxy_pass http://127.0.0.1:3000; } location = /favicon.ico { access_log off; log_not_found off; } location = /robots.txt { access_log off; log_not_found off; } access_log off; error_log /var/log/nginx/{{ SITE }}-error.log error; location ~ /\.(?!well-known).* { deny all; } } # FORGE CONFIG (DO NOT REMOVE!) include forge-conf/{{ SITE }}/after/*; ``` You may notice that the `location /` block is using `proxy_pass`. Server-side rendering in Next works similar to PHP, the server keeps a process running that generates the content and serves it to the client. With Next.js, we’re using Node, so we’ll pass our requests to the Next.js server via port `3000`. You can change this based on your project requirements. ## Creating The Site With the Nginx Template created we can now create our site, making sure that we select the “Next.js App” Nginx Template option:  Once Forge has created the site, we can install our repository from our chosen Git provider. ## Deployment Script The next step is to update the site’s deployment script: ```sh cd /home/forge/next-app-static.curved-feather.test git pull origin $FORGE_SITE_BRANCH npm install ``` We can now deploy our site with the updated script to have our NPM dependencies installed. If we browse to our site now, Nginx will give us a 502 error. This is because we’ve yet to start the Next.js server. To do, this we’ll create a new Daemon on the server. For the daemon, we only need to provide the directory of our site and the command; `npm run start`.  Once the Daemon is configured and becomes active, we can visit our site and see that it is now working.

In this article, we'll cover the Vapor most common infrastructure performance tips that may speed your Laravel applications powered by Vapor.

A whole month has flown by since our [last post](https://blog.laravel.com/forge-april-round-up) which rounded up all of the things we shipped to [Laravel Forge](https://forge.laravel.com) in April. This month we've also been refactoring parts of Forge, laying the ground work for some exciting new things... SSL Default Sites ----------------- When Forge provisions an App or Web server it creates a "default" site. This site is served by Nginx when a request is made to your server for a domain that has not been configured. Previously, when a server had configured SSL for one of its domains, Nginx would avoid using this default site and instead serve the first domain that was listening on port 443. To prevent this, Forge will now create a default site for SSL requests as well. Site Log Improvements --------------------- The Log panel will now try to display logs from additional paths. This is especially useful when using Forge in combination with services such as [Envoyer](https://envoyer.io), which stores log files in nested folders. Furthermore, Forge will also attempt to display log files from WordPress sites. Modern Server Defaults ---------------------- Forge will now provision servers with Node v14.x by default. Previously, v12.x was installed. PHP 8.0 is now the default version when creating a new server. Of course, you're free to change this as per your requirements. Ubuntu Version Warning ---------------------- If your server is running Ubuntu 16.04 or lower, Forge will warn you that your server is out of date and give advice on how to migrate your server to Ubuntu 20.04. The version warning is visible in your site's deployment output. Database Backup Improvements ---------------------------- The improvements to the Database Backups feature just keep coming! You're now able to quickly select all databases when creating a new configuration, but in keep in mind this will not include databases created **after** the backup. When creating a backup configuration using AWS or DigitalOcean spaces, Forge will now quickly validate the credentials too. Extra Bits ---------- DigitalOcean's AMD offering is now available in more regions, so we've reflected this in Forge too. You can now additionally select AMD as your server type in the AMS3, BLR1, LION1, NYC1, SGP1 and TOR1 regions. Hetzner server types are now listed with their identifier, for example `CX11` etc, making them much easier to find when creating your server. And finally, when a server has finished provisioning, Forge now creates a lock file that prevents provisioning from happening again. 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.