DA Pro support php 5.2 - latest version and unlimited version of installation.

M

mean

Verified User
Joined
Feb 14, 2007
Messages
113
-------------------------
Please Vote
-------------------------

Upvoty

feedback.directadmin.com feedback.directadmin.com

-------------------------

Is it possible for Directadmin Pro to support PHP 5.2 - the latest version and it supports more than 4 versions of PHP.
Unlimited version of installation. and no need to use cloudlinux.

I understand that Plesk also supports PHP 5.2 - the latest version,

# 1 )
I believe it will be a feature that will encourage many people to upgrade to the Pro Version.
Many customers would choose to use Directadmin.

because this is still a weakness that Plesk and cPanel have an advantage over.

# 2 )
Currently, there are issues with the compilation of PHP versions. , debian cannot compile 7.4 before 5.6
php1_release=8.2
php2_release=5.6
php3_release=7.4

ref

PHP 5.6 with htscanner=yes fails compilation on Debian 10

I'm not sure if PHP 5.6, htscanner=yes and Debian 10 is the only combo this fails on, but this is what I'm trying right now. # grep ^php._release options.conf php1_release=7.4 php2_release=8.0 php3_release=5.6 php4_release=no # grep ^htsc php_extensions.conf htscanner=yes A fresh DA setup...
forum.directadmin.com forum.directadmin.com

# 3 )
PHP Version Selector move to Dashboard
( oh i see will update on v1.651 )

# 4 )
PHP Extension Selector by user , If it can be done.

# 5 )
I encountered a problem when transferring users between servers with different PHP version numbers.
if the PHP version is not supported, website it will not be functional.

I think you should change the usage of PHP1, PHP2, PHP3, PHP4 to PHP{version} as specified in
/usr/local/directadmin/data/users/{USERNAME}/domains/{DOMAIN}.conf
php_selector=php7433

If you have plans to do it again I think you made it support the php patch version.

#6 )
Idea config for custombuild/options.conf

# new format
php{version}=yes,no​
php{version}_mode=php_mode​
... or ...​
php{version}={yes,no},php_mode​

# minor and patch versions. (i like this)
php7433=yes,php-fpm​
php823=yes,php-fpm​
php824=yes,php-fpm​
... or ...​
php823=yes​
php823_mode=php-fpm​

# support only miner versions
php82=8.2.6,php-fpm​
php83=no <-- when i need disabled.​
... or ...​
php82=8.2.6​
php82_mode=php-fpm​

#7 )
PHP Selector option (ON/OFF) for auto swap php version when php already have upgraded.

#8 )
Plesk will be build php installed package for any os. , understand that cloudlinux does it too.
https://autoinstall.plesk.com

Please share your IDEA.....

--------------------------------------------------
Happy 20th Anniversary
Directadmin.com (2002 - 2022)
--------------------------------------------------

We are DA Lover , 17 years ago.
Thank you so much for your hard work.
sorry my english not good.
CJ.
 
Last edited:
I understand about EOL and it's difficult.

However, in the future, setting up php{version} format is definitely better than php{number} certainly.
have been a problems for a long time about this format (php1,php2,php3,php4)

I have transferred more than 1,000+ websites from the old server to a new server.
I encountered numerous issues with mismatched PHP{NUMBER} versions and had to spend time replacing to make compatible.

At least in the future
/usr/local/directadmin/custombuild/option.conf
php82_release=yes
php82_mode=php-fpm
php74_release=no
php74_mode=php-fpm
php56_release=no
php56_mode=php-fpm
php53_release=no
php53_mode=php-fpm
Click to expand...

/usr/local/directadmin/data/users/{USERNAME}/domains/{DOMAIN}.conf
php_selector=php74
Click to expand...

I know cloudlinux is good choice for multi php versions, I often see the DA Team speaking like that.
But wouldn't it be better if the DA supported this functionality?


Kind Regards
 
mean said:
But wouldn't it be better if the DA supported this functionality?
Click to expand...
Not to my opinion, because it would mean a lot of more work. I know for example that cPanel still provides it, but it does not support it. It's "as is" so any issue rising with EOL versions is on your own risk.

So this is also why I personally would not like DA to use this option, because this only gives more chance for more servers to run unsafe versions of EOL php versions, with all risks included. Not only for the owner, but also for others, as hacked systems can easily again be used by spammers or for DDOS attacks, which is also not good for others who do have their systems in up to date order.

Next to that, it keeps giving customers the idea that they don't ever have to do anything and just keep using their ancient stuff, with all risks involved.
Because in spite of the fact that Cloudlinux does secure the php versions, but not older WP and Joomla sites with their old addons, which again can lead to hacks and spammers which we all suffer from.

I'm personally a great upholder of trying to be as up to date as possible and teach the customer that upgrading is just something which needs to be done. Ofcourse a bit late, like running PHP 7.4 still at this time, can be thought of, but in november that's also a year and then it's really time to change, at least to 8.0.

Anyway, just my 2 cents and thoughts and I know a lot of people disagree, mostly because of being afraid to loose customers.

P.s. I don't want to start a discussion here, it's just how I think and I understand others have other opinions about it. So we can just agree to disagree without the need of discussion.:)
 
It's hardly compilled manualy even on EOL Centos7 (I spent half a day and must drop few parts), I'm not sure DA will waste their programmers time/money to add this feature and adapt for modern OS. So if your client want to keep ancient things working and don't want to pay programmer for website update - it will cost him pay for ready working things like Cloudlinux. If you don't want change current server - you can rent small VPS for and collect such old things there (I do same) so there no need to install Cloudlinux on all servers.
 
Thanks for the feedback @mean! Quick notes on the first two ideas:

PHP 5.2. We are not planning to add support for older PHP versions. (y) for @Zhenyapan and @Richard G comments.

PHP build order issue.This issue is fixed in latest release (DA 1.651), at least the htscanner build code :). With each update CustomBuild is slowly being upgraded to use clean reproducible builds. Instead of building multiple stuff in existing sources directories it always creates fresh temporary dir which gets wiped out after build. For PHP plugins we are upgrading CB to build them for each PHP version separately in clean environment. This is visible in the CB updates section, where some plugins now report updates for each PHP version.

Multiple PHP versions. Parts of CB is being refactored to support more than 4 different PHP versions. With this change we will need to revisit how PHP versions are stored in configs and will try moving away from PHP slot numbers 1,2,3,4 to just PHP versions 7.4, 8.2,... , so that migrating user account which used PHP 7.4 as PHP1 to server where PHP 7.4 is used as PHP2 would work without changes. But this is not trivial since we need to have backwards compatibility for backups made with older DA versions :).
 
Hi @fln

It is indeed great news that you will be improving the PHP slot number in the future.
I hope that it will also improvements into the DirectAdmin (Lifetime) License : )

You should start by storing the PHP version for each domain in the "backup.user.tar" file.
When you restore the file on a new server, it will make it easier to ensure compatibility.
and create a new migration script into directadmin/scripts/php_migration.sh

I think this should be improved to increase long-term efficiency
because it has been a problem since the early days of multiple PHP versions.

Thank you so much
 
Last edited:
You must log in or register to reply here.
Back
Top