Vestacp template suggestion...
Posted: Sun Sep 09, 2018 6:13 am
Hi,
From the vestacp docs stated:
"File with sh extension is optional. It can be used as trigger to run additional shell commands on domain creation."
First question:
Why vestacp only provide a template on domain creation but no template on domain destroy?
I have managed to make vestacp to works with apache + phpfpm. But when deleting a domain i have to manually delete fpm pool for that domain. Doesnt it will be easier if vestacp provide a template that triggers on domain destroy as well?
Unrelated suggestion:
as we know that vestacp still use apache+prefork modphp which is the really really oldest method. I think it exist since my grandpa still young. Jk. and have been deprecated as well. That is official statement from apache here https://wiki.apache.org/httpd/php
Why vestacp still use this apache+prefork+modphp? Even cpanel (based on apache) which known to slow adding new software (they do this on purpose because millions of website will crash if the software is still not stable). Even cpnel already ditch modphp and set phpfpm as thier default php handler.
Well since adding apache+phpfpm will need to change a lot of vestacp current software. I propose to add template on destroy feature. That will make it much much easier to migrate to apache+phpfpm.
From the vestacp docs stated:
"File with sh extension is optional. It can be used as trigger to run additional shell commands on domain creation."
First question:
Why vestacp only provide a template on domain creation but no template on domain destroy?
I have managed to make vestacp to works with apache + phpfpm. But when deleting a domain i have to manually delete fpm pool for that domain. Doesnt it will be easier if vestacp provide a template that triggers on domain destroy as well?
Unrelated suggestion:
as we know that vestacp still use apache+prefork modphp which is the really really oldest method. I think it exist since my grandpa still young. Jk. and have been deprecated as well. That is official statement from apache here https://wiki.apache.org/httpd/php
Why vestacp still use this apache+prefork+modphp? Even cpanel (based on apache) which known to slow adding new software (they do this on purpose because millions of website will crash if the software is still not stable). Even cpnel already ditch modphp and set phpfpm as thier default php handler.
Well since adding apache+phpfpm will need to change a lot of vestacp current software. I propose to add template on destroy feature. That will make it much much easier to migrate to apache+phpfpm.