Using a package custom web template does not take affect

I copied /usr/local/hestia/data/templates/web/apache2/php-fpm/default.tpl (and stpl) to /usr/local/hestia/data/templates/web/apache2/php-fpm/hosting1.tpl (and stpl).

I made changes to those new files.

The new template shows up in the Packages, and I change it.

I rebuild web-domains … but the apache2.conf file for the user’s domains does not change. It is still the same.

If I change it in the individual domains, then it works … but WHY does it not work with the package settings? The package settings should make it change in all of the domains instead of having to change them individually.

Because changing the template inside of the package should not directly update all web domains - usualy, in hestia and even with an fpm installation, you have a great variation of used templates. You don’t want to have this changed at all over the package settings.

Possibility would be to change it trough a small bash script, loop trough users, loop trough all webdomains and do a v-change-web-template (or similar). If you know what you’re doing, you can get chatgpt to help you with that - so it should not take more than 5 minutes.

But overall; it’s the correct way to not overwrite the template settings within package configuration.

1 Like

Ok, I see. So those template settings in the package only affect new users/domains that are created after the change to the package. Thank you for that information.