Nginx App Templates
Clone, edit and delete reusable Nginx application templates with scope, naming and generation precautions.
Open Web Servers → Nginx → Nginx App Templates.
Scopes
Supplied global templates can be cloned. Global custom and account custom templates can also be edited or deleted through the available row controls.
Domain generation checks an account template before a global custom template and then a supplied template. Same-named definitions can therefore behave differently for different accounts. The global Settings selector is limited to its supplied choices; choose custom profiles through domain workflows.
Clone
- Choose the source template.
- Select the global or account clone action.
- Enter New Template Name and Description.
- For an account clone, select Account Username.
- Click Create Template and inspect the result.
| Field | Validation |
|---|---|
| New Template Name | Up to 200 letters, numbers, dots, underscores or hyphens. |
| Description | Required, maximum 200 characters. |
| Account Username | Existing valid account for account clones; maximum 31 characters in this form. |
Global clone names cannot begin or end with dot, hyphen or underscore. Both clone paths reject an existing destination using the submitted name. The copy helper lowercases the destination name, so use a unique lowercase name and check existing names without relying on case differences.
The helper copies the file and updates shared application-description data. If the latter fails, a copied file may already exist; inspect before retrying.
Edit a custom template
Open its editor, preserve a copy of the current content, edit the template, click Save Template and confirm. The editor identifies the syntax as Mako.
The save operation requires content but does not perform a complete rendering or Nginx configuration test before writing. It does not automatically rebuild every domain using the template.
Validate before applying
A saved template can still contain invalid generation logic or Nginx directives. Verify it with an intended domain and retain the working original before rebuilding consumers.
Delete a custom template
Use its delete action, review the named template and confirm. Supplied global templates are protected from ordinary edit/delete operations.
Check every domain using the template before removal. A broader same-named template or the configured fallback can change future generation; missing or incompatible definitions can break a rebuild. Deletion is not a consumer-aware migration.
Demo sessions cannot clone, edit or delete. After changing a template, deliberately rebuild the intended consumers and verify their configuration and responses.