TUTORIAL: PHP selector for PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.4 for Debian & Ubuntu (and optionally directly nginx-PHP-FPM)

[jodumont]

Hi;

I was wondering how to make it happen without apache
like if I installed only nginx+php-fpm on Debian9

[dpeca]

Hi;

I was wondering how to make it happen without apache
like if I installed only nginx+php-fpm on Debian9

See second post in this thread, but, however, you probably need to modify tutorial steps (from first post) to avoid Apache-related things.

Or simply install Apache, follow tutorials from first and second post, and then simply turn off Apache.

[eSzeL]

Hi!

Thank You for your help, I managed to use the default PHP 7.2 with Apache 2.0 Handler, and PHP 5.6 with FPM/FastCGI on Ubuntu 18.04 LTS.

My question is: why these pool.d PHP FPM config files are left behind after deleting a user / domain:
/etc/php/5.6/fpm/pool.d/domain.com.conf

After that, php5.6-fpm service restart also fails.

Thank you, in advance!
Sincerely,
eSzeL

[eSzeL]

I added this line to /vesta/func/domain.sh, to the del_web_config() function:

# Delete web configuration
del_web_config() {

rm -f "/etc/php/5.6/fpm/pool.d/$domain.conf"

Hi!

Thank You for your help, I managed to use the default PHP 7.2 with Apache 2.0 Handler, and PHP 5.6 with FPM/FastCGI on Ubuntu 18.04 LTS.

My question is: why these pool.d PHP FPM config files are left behind after deleting a user / domain:
/etc/php/5.6/fpm/pool.d/domain.com.conf

After that, php5.6-fpm service restart also fails.

Thank you, in advance!
Sincerely,
eSzeL

[dpeca]

My question is: why these pool.d PHP FPM config files are left behind after deleting a user / domain:
/etc/php/5.6/fpm/pool.d/domain.com.conf

Because this tutorial does not modify Vesta sctipts in any way - you must implement deletion manually - as you already did.

[eSzeL]

I see.. Next question: how can I modify it in a more future proof way?

Because this tutorial does not modify Vesta sctipts in any way - you must implement deletion manually - as you already did.

[dpeca]

I see.. Next question: how can I modify it in a more future proof way?

Probably there is no way to do it - except to fork Vesta on github and stop regular updates of vesta and update vesta only via github (from your fork) - which means you also should merge origin-master official vesta git repo to your fork frequently.

[Jexs]

I just would like to note that dpeca's suggestion has been implementd among many other improvements in HestiaCP, a VestaCP fork.

Is HestiaCP considered secure? At least as much as Vesta is?

[alexcy]

Definitely more secure. VestaCP wasn't very secure lately..

[imperio]

Definitely more secure.

for example? hestia is fork of vesta