Hello Guys,

Most of our customers are using multiple PHP versions per website via EA-PHP on cPanel. Now when we move to Enhance, they will just have one PHP for their entire account/website. In Enhance PHP can be set on the website level but not on the addon domains level. I would like to register a feature request where clients can select the PHP version for their domain.

Each website on Enhance can have its own PHP version.

Domains (aliases/addon/parked/subdomains) share a PHP container and php-fpm or lsphp instance. Supporting multiple versions within a single website would require multiple instances of php-fpm or lsphp within a single container.

It's not impossible. Is this something other customers would like?

i do not see the use for that to be honest, one version per domain/container would be sufficient.

i would say that providers (or clients) that are used to PHP Selector from Cpanel, would preffer to be able to select the PHP Version per website.

and providers or clients (like me) who are used to PHP Selector of CloudLinux, find enough the php selector per account.

Yes, I have similar understanding that 1 PHP controller per account is enough. But some people keep running legacy apps and need an older version. Maybe I will ask them to buy another plan or so! Let's see what happens.

2 years later

+1

+1

Found nothing but dramas supporting sites with PHP Handlers and multiphp with cPanel.
This is such an obscure requirement and quite frankly one that should not exist going forward into 2025.

Let's get real, the PHP version these 'legacy' sites are on are very likely no longer supported.
These ticking timebombs are exposed to the internet, they absolutely should be isolated to their own website containers. If you are hosting such an abomination that requires multiple php versions at a directory/file level, charge the customer $2000/mo to cover the cPanel licence and supply of xanax!

KISS: Keep It Simple Stupid. - One PHP Version per Website

    cosmoshosting One PHP Version per Website

    Sure, then Enhance need to "enhance" the limits to be per Website, and not per Package 🙂.

    • rdbf replied to this.

      adil

      Then call it WebSpace, and have your package have one webspace with infinite websites as subdomains/add-on domains with app installations.

      Having multiple Enhance websites in a package makes no sense. Packages should have 1 Enhance website.

      Write a Reply...
      Follow @enhancecp