


MailBee Message Queue Queue-based background sending of emails.MailBee Objects ActiveX email components: SMTP, POP3, IMAP, S/MIME.NET service to deliver e-mails in the background NET email components: SMTP, POP3, IMAP, EWS, Security, AntiSpam, Outlook, Address Validator, PDF

Only for ISPmanager Business and if the reseller is not a user's owner The table below contains a list of variables regardless a web-servers type. The following list contains standard variables for each WWW-domain management function. Standard variablesĮvery function you call uses its own set of parameters that are passed to a session. Only ErrorDocument 404 will be used to search for our parameter, thus it will be found and deleted in the configuration file. Deleting of an error page will set the $ERROR variable to off, therefore the condition used in the template, won't be met. But in the template the $URI value is canceled, the search will be made by the ErrorDocument 404 string. If we decide to delete the error page from the control panel, the template engine won't find a required parameter in the configuration file and won't delete it. In this case, the ErrorDocument parameter differs from the one specified in the control panel. We have the following configuration file:

Then, we decided in the configuration file change the path from /404.php into /404.html. During that process, the $ERROR variable is set to on, therefore the condition is met, and our configuration file looks like that: The $CODE and $URI values are specified in the control panel on the error page creation form. If the $ERROR variable is on, the ErrorDocument parameter with variables $CODE and $URI will be added into VirtualHost. These tags define values that won't be used during the search process. This expression is interpreted as a common variable but plays a specific role in parameter search. They can contain only variables, such as. Searching for a modified parameter by key values However, if you are trying to modify those parameters in the configuration file, they are likely not to be added into a required section but will be applied in a new section. Therefore, when something should be added or deleted from the configuration file without a control panel, the template engine "knows" exactly where to perform the operation. for the Nginx configuration file, server_name and ssl are selected as key parameters. Parameters that identify sectionsĮvery type of configuration file has certain parameters that are used by the template engine to identify sections. The table below shows correspondence between a file with a template, and a function to call in the SyntaxĪll template sections must locate between tags Įnter an absolute path to a template you want to import. When the panel updates, files in the /usr/local/mgr5/etc/templates/default/ directory will be overwritten, that's why you should make changes in /usr/local/mgr5/etc/templates/. If the /usr/local/mgr5/etc/templates directory contains a template file, the template in the /usr/local/mgr5/etc/templates/default/ directory will be ignored. Copy a file with template into the /usr/local/mgr5/etc/templates directory with the same name. In the web-domain creation/edit function has a corresponding template in the /usr/local/mgr5/etc/templates/default/apache2-vhosts.template file for Apache configuration file, and /usr/local/mgr5/etc/templates/default/nginx-vhosts.template for Nginx.įiles with configuration templates can be re-defined by user parameters. The template engine will be used by default to generate configuration files of the "WWW-domains" module. This article will walk you through the steps you need to perform to start using a template engine, describe its general functions and syntax. Besides, after you add user parameters into the configuration file, other operations that the template engine performs, won't modify them. With this mechanism, you can use the required parameters in order to configure Apache and Nginx. The mechanism is based on a template that enables to use logical branches and parameter setting, allowing for more flexible creation and modification configuration parameters of a web-server. A new mechanism that allows generating Apache and Nginx configuration files.
