Conf-custom upgrade ISPConfig version

Hello,
I’m currently testing ways to automate the ISPConfig upgrade using Ansible.
There are configuration files, such as main.cf, dovecot.conf and the amavis 50-user file, which I modify during the installation process to apply the settings I need.
I have seen and read that ISPConfig has a conf-custom directory where you can place the templates you want to be applied.
I’m currently trying to create a template for Amavis; I’ve saved it both in the root of conf-custom and in conf-custom/install, named amavisd_conf.master and amavisd_custom.conf.master, but when I perform the upgrade, this configuration isn’t applied; instead, the default settings installed by ISPConfig are used.
Is there something wrong with the filename or the path?
Is there any documentation that specifies the naming convention and path for where to place these files?

Translated with DeepL.com (free version)

 

OK, thanks, it worked for me!!

 

Hello,
I sometimes set up Nginx in front of Apache, with Nginx listening on port 80 and Apache on ports 8888 and 443.
To ensure the sites are configured correctly in Apache, I usually edit the file /usr/local/ispconfig/server/conf/vhost.conf.master, but I can’t find it in the path you’ve given me.
I’ve seen the file apache_ispconfig.vhost.master, but I’ve looked at it and modified it, and it doesn’t make the change I need in the vhost.conf.master file.
Can you advise me on which file I need to put in conf-custom?

 

OK, but I’ve already tried copying the file /usr/local/ispconfig/server/conf/vhost.conf.master to /usr/local/ispconfig/server/conf-custom/install/vhost.conf.master with the settings I need, and when I update the ISPConfig version, it overwrites it with the default ISPConfig file.

 

Ok Thanks!!!

 

Hello,

Thank you for the information; it’s helping me to automate the ISPConfig update as much as possible, but I’ve come across a strange issue and wanted to ask if you could offer any guidance.

I have created the main.cf template for Postfix in the path you specified and with the name you indicated, and when I run the update, everything works fine except for a few Postfix variables, which the update modifies even though they are declared in the template file.

virtual_transport = dovecot -> virtual_transport = lmtp:unix: private/dovecot-lmtp
address_verify_transport_maps = $transport_maps -> address_verify_transport_maps = static:smtp:[127.0.0.1]:10025
address_verify_virtual_transport = $virtual_transport -> address_verify_virtual_transport = smtp:[127.0.0.1]:10025
content_filter=amavis:[127.0.0.1]:10024 -> content_filter = lmtp:[127.0.0.1]:10024

Could you tell me why ISPConfig changes these settings during the update if I have defined them differently in the template?

 

I think /conf-custom/install/ folder is also meant for update too, other than install, so to survive update, a copy of custom template must be in there too? Of course not all template files. Also, to ensure the template file in /conf-custom/install/ is the same with /conf-custom/, if both need to exist, try to use symlink.