Stratus Panel - Nginx > Includes
Nginx includes are easy to add in Webscale STRATUS, but can be difficult to master. Incorrectly coded includes can result in undesirable results and should never be added to a Production environment without fully testing on another environment.
The following are two examples provided by Stratus customers. Do not use these as-is on a Production environment and always test all includes on a non-Production environment before deploying.
WordPress
Add this to get WordPress working in a subdirectory of your web-root, substituting the blog path for the particular sub-directory.
location /blog/ {
index index.php index.html index.htm;
try_files $uri $uri/ /blog/index.php?$args ;
location ~* \.php$ { try_files /dummy @proxy; }
}
location /blog/wp-admin/ {
index index.php index.html index.htm;
try_files /blog/wp-admin/$uri /blog/wp-admin/$uri/ /blog/wp-admin/index.php?$args ;
location ~* \.php$ { try_files /dummy @proxy; }
}
Custom PHP Scripts
The default Webscale STRATUS Nginx template does not allow PHP execution in directories not normally required by Applications. A special Nginx location is required if you have custom scripts or other PHP based code you need to run.
location ~* my_custom_scripts/ {
try_files $uri $uri/ /index.php?$args;
location ~* \.php$ { try_files /dummy @proxy; }
}
Change my_custom_scripts in the example above to match your requirements.
Last modified on June 3, 2026