Learn how to use Nginx templates to customize your site configurations.
Variable | Description |
---|---|
{{DIRECTORY}} | The site’s configured web directory, e.g. /public |
{{DOMAINS}} | The site’s configured domains to respond to, e.g. laravel.com alias.laravel.com |
{{PATH}} | The site’s web accessible directory, e.g. /home/forge/laravel.com/public |
{{PORT}} | The IPv4 port the site should listen to (:80 ). If the site name is default , this variable will also contain default_server |
{{PORT_V6}} | The IPV6 port to listen to ([::]:80 ). If the site name is default , this variable will also contain default_server |
{{PROXY_PASS}} | The PHP socket to listen on, e.g. unix:/var/run/php/php8.0-fpm.sock |
{{ROOT_PATH}} | The root of the configured site, e.g. /home/forge/laravel.com |
{{SERVER_PUBLIC_IP}} | The public IP address of the server |
{{SERVER_PRIVATE_IP}} | The private IP address of the server, if available |
{{SITE}} | The site’s name, e.g. laravel.com . This differs from {{DOMAINS}} in that it does not include site aliases. |
{{SITE_ID}} | The site’s ID, e.g. 12345 |
{{USER}} | The site’s user, e.g. forge |
site:manage-nginx
permission. This permission is also used to restrict the ability to edit an existing site’s Nginx configuration file.