NGINX Templates: Save, reuse, and centrally manage your configs

Announcements
1

NGINX Templates let you save, reuse, and centrally manage your server configurations across all your web applications.

image
image2048×1040 229 KB

Save your optimized NGINX configs as reusable templates, install them on any web app with a single click, and push updates to all linked apps when your config changes.

Learn more about NGINX Templates →

How It Works

You can now save your NGINX configurations as reusable templates at the account level. Create a template from scratch or from any existing web app’s config. Templates support variables like {{webapp_path}}, {{php_version}}, and {{username}}, so the same template works across different apps and servers.

Install on any web app: Use templates during web app creation or attach them to existing apps. You can attach up to 5 templates per web app: one for security headers, one for caching rules, one for routing, etc.

Update everywhere from one place: When you need to push a change (say, a new Permissions-Policy header), edit the template once, select which linked web apps to sync, and RunCloud handles the rest. One NGINX reload per server, done.

You’re in control:

  • Conflict detection warns you if a web app has local edits before you overwrite them
  • Detach any web app from a template for independent customization
  • Browse the public template library, duplicate community templates, and sync upstream updates manually
2 Likes
2

How can we publish community templates?

3

Hey @Arvoisa,

This is not currently supported: Introduction to NGINX Templates | RunCloud Docs

NGINX public templates are predefined ones by us, and you have your own private library of reusable templates that you can create in your workspace.

What templates were you thinking of publishing?

We may look into a way to credit people but still include a manual step (for the obvious reason that they need to be verified manually).

4

Are there any plans to make NGINX configurations available through the REST API?

5

Here is one.

This is what we use do deliver webp images in WordPress. There could be alternative version for avif and one that supports both:

set $webp_suffix "";
if ($http_accept ~* "image/webp") {
    set $webp_suffix ".webp";
}

set $webp_bypass "";
if ($arg_no_webp = "1") {
    set $webp_bypass "_off";
}

location ~* ^/.+\.(png|gif|jpe?g)$ {
    add_header Vary Accept;
    try_files $uri$webp_suffix$webp_bypass $uri =404;
}