Appendix C. Customizing Server Configuration Files by Means of Templates

You cannot customize some major service configuration files (for Web, mail, DNS, databases) directly, as your changes in these files will be overwritten with a consequent Parallels H- Sphere update! Instead, you need to create configuration file templates by means of the hsphere-update wrapper and customize these templates instead of default configuration files.

You can customize config file templates by means of Parallels H-Sphere updater, provided you have not customized your templates already. For this purpose two new options are added to the hspackages wrapper of the Parallels H-Sphere update script:

• hspackages ctemplates=[OPTIONS] - Place custom templates for comma-separated list of services into predefined locations if custom templates are not there already.
• hspackages edit=IP:/path/to/custom/template - Edit custom template on a specified server in a specified location.

Important:
If you run the hspackages ctemplates command without options, it will create custom templates on all related servers of the Parallels H-Sphere cluster! To specify particular servers where custom config templates should be created, please use the extended syntax of the hspackages command. For example, to create PHP custom config templates only on the physical boxes 192.168.1.10 and 192.168.1.11, run:
hspackages ctemplates=php ips=192.168.1.10,192.168.1.11
The hspackages ctemplates command should be run only once, in order to create custom config templates! Then you customize these files according to your needs. Next time you run it, it will prompt re-creating your custom config templates, thus you may lose your customization!
The only exclusion when you need to run hspackages ctemplates again is when a coming version of the hsphere-update package contains updates of default config templates. You will be specially notified of this in the respective update notes.