Manual modification of web-server configuration files
Introduction
ISPmanager 6 uses its own database to store the configuration of a WWW-domain. Very often, a server administrator modifies configuration files not in the domain's edit form, but directly in the configuration file. In this case, when he edits a WWW-domain in ISPmanager, his manual changed will be lost.
To save manual changes, when the WWW-domain edit form opens, ISPmanager reads its configuration file and add modified values into its own database.
How it works
Sometimes it may happen that a value is modified in the Nginx configuration file, but is not changed in Apache, etc. In that case, take the note of the following information:
- The Nginx configuration file has the priority (except for values specific for Apache, such as "List of CGI extensions")
- The Server or VirtualHost section, which accepts SSL-connections, has the highest priority within one file
When a user opens the WWW-domain edit form, he will be informed what fields have been changed.
List of parameters
The following parameters are added to the database:
| Parameter name on the field | Database field |
|---|---|
| Encoding | charset |
| Index page | dirindex |
| SSL-port | ssl_port |
| CGI-scripts | cgi |
| Files extensions (CGI) | cgi_ext |
| Access log | log_access |
| Error log | log_error |
| SSL | strict_ssl |
| SSI | ssi |
| Compression | srv_gzip |
| Compression level | gzip_level |
| Caching | srv_cache |
| Caching period | expire_period |
| Period value | expire_times |
Disabling functionality
In order to disable the described functionality, use the Option DisableWebDBReadConf option in the Configuration file.