Webserver Application Templates
Customize Apache, Nginx and OpenLiteSpeed virtual-host templates with account and global overrides for the selected website application.
These Mako templates generate website virtual hosts for an application selection such as a default site or a particular runtime. They are separate from control-panel plugin packages.
Application template locations
Use the following engine directory name: httpd, nginx or openlitespeed.
| Priority | Location |
|---|---|
| Account override | /var/eenos/userdata/<user>/templates/<engine>/<app> |
| Global custom | /usr/local/eenos/templates/webserver/<engine>/custom/<app> |
| Shipped default | /usr/local/eenos/templates/webserver/<engine>/<app> |
The app selection is the filename. If the requested application template is unavailable, the relevant builder can fall back to its configured default. Confirm the actual selected path and resulting vhost instead of assuming the requested file was used.
Match the deployed web stack
Choose the engine actually serving the site. A proxy deployment can need both frontend and backend templates. Preserve paths, ports, TLS handling, logs, upstream sockets, ownership and security includes required by the current builder.
Other server-level files such as nginx.default, httpd.settings and suspension templates have separate selectors under webserver/ and webserver/custom/. An app-template override does not replace every global or suspended-site configuration.
Rollout
Copy a compatible current template into a supported custom location. Stage the generation for a representative site and inspect both HTTP and HTTPS configurations. Use the selected webserver's native syntax/configuration checks before an intentional reload.
Do not remove generated security or accounting directives merely to make a custom application work. Preserve a working template/configuration pair for rollback, and compare custom files with shipped updates. See Apache, Nginx and OpenLiteSpeed guides for service operations.