It will be good if it is possible to setup a php version per domain and not only per website.
If inside a website are different domains with different php version it would be nice to setup this individual.
PHP Version per Domain
This is already possible, just setup a separate website. You will run into issues trying to save a few $$'s by using add-on domains. Instead, use Enhance how it was designed to be used.
PS It's not practical for performance and security reasons to have a user server websites with different versions of php.
Hi, it is not because of $. It is because of request at my customers. No issue. I will let them know that it will be changed. They was know that from previous panel. 
And I only compare with it and ask. Sorry.
xyzulu Its not about $$ its about clients who are migrated from cpanel with multiple websites, there is no easy way to separate them into different "websites", also there are clients who NEED different PHP version for folders and have get used to that from other panels, its something that NEEDS to be added along with better backup handling in the APP tab
SeLi Hi, it is not because of $. It is because of request at my customers. No issue. I will let them know that it will be changed. They was know that from previous panel.
No need to be sorry. to be able to use different php version u need to create a new website. but you also should care about $$ as creating multiple websites within the same package will multiply the resources allowed.
xyzulu If you do that, the CF integration will no longer work simultaneously for both the domain and the subdomain (as I recall). There’s no reason not to keep things separate, even if they share the same container. Even backups aren’t entirely independent. Restoring a backup for the main domain also restores the subdomain, even if you only intended to recover one site.
- Edited
gmakhs its about clients who are migrated from cpanel with multiple websites
The fact that a function works on cpanel, does not mean that the same function MUST also works on enhance. The addons here do not exist to create infinite sites under a single package, the entire structure of Enhance is studied and designed to manage "multiple customers with their websites", so if you choose a platform, you have to use that platform at its best, and not try to use it as cpanel. I know it isn't easier to move them out, but keeping them inside then you have to accept their limitations.
Different PHP for different "folder" should be created as different website too, so they can have their PHP, their ini, their redis, their backup, and so on (and I'm quite convinced that what we're calling "a folder" is actually a site that lives its own life, then exceptions exist, of course, but I'm talking about the rule and not the exception).
- Edited
Depends on your cloudflare tier if I recall correctly. Free tier doesn't have subdomains as separate zones. Paid you could make them separate and have separate API keys
rdbf Anyways, there‘s no reason not to make separation possible. Leave that decision to me, the admin. I like the idea of having the subdomain within the same container as the main domain, but I don’t like how it’s managed. Any change made to the main domain also affects the subdomain, which isn’t ideal.
- Edited
Because
1) those are clients that have been migrated from cpanel and have multiple websites that are not keen to migrate separately
2) because giving them extra website it also gives them extra resources on the server ? Imagine doing that on a customer with 20 "app" and instead of one website giving him 20 now that client has 20x the resources allocated
3)Something being used by literally by almost any other panel in the market , makes it a market standard - default that most clients expect and ALSO makes it necessary so you can migrate such clients .
With respect, while it does make sense when you look from the cPanel perspective. But that is what it is... a cPanel perspective.
I don't believe Enhance is intended for multi-domain per account support.
Enhance is designed to be sold per website / per domain.
gmakhs 2) because giving them extra website it also gives them extra resources on the server ? Imagine doing that on a customer with 20 "app" and instead of one website giving him 20 now that client has 20x the resources allocated
3)Something being used by literally by almost any other panel in the market , makes it a market standard - default that most clients expect and ALSO makes it necessary so you can migrate such clients .
I was under the impression that if you setup reseller accounts, then you could put a secondary limit on "ALL WEBSITES" vs. PER WEBSITE.
So technically you could make a customer a reseller and separate the websites? I could be wrong - I do not operate this functionality.
+1 for me
From my perspective, it is important to run different PHP Version within a "website package" - which is a hosting package for the customers domains, and he pays exactly for that single package. To add a "new" website to a customer does mean twice the ressources will be used. This is not only "cPanel view" - it is industry standard as well.
A feature request for this already exists. Please check out and continue the conversation over at https://community.enhance.com/d/444-php-version-per-domain
Aliysa_Enhance locked the discussion.