[ QApache 2.4.39 + PHP 7.2.29 ] WebServer with PHP and PECL

[QNAP_Stephane]

it is just an extension issue, may be due migration version..

anyway you will soon turn to 64bit, and will have to reinstall Qapache new version

I will stop supporting the x86 32bit version, FW 4.3 will turn all NAS into 64bits system

I am actually building the last version.. with i hope an arm-x41 version as well

[zwarteraaf]

I am already on 4.3. and used your 64 bit version

[QNAP_Stephane]

update pending

Apache 2.4.25 + PHP 7.1.0

arm-x41 already available (in upload)....

x64 version (in debug)

[DJCMBear]

How much more work would it be to package a qpkg for firmware 4.2.2? I don't want to update to version 4.3 just yet as my NAS is used daily.

I am in the works of building a 100TB NAS which will use 4.3 but that isn't going to be live for a few months and I would really like to use apache 2.4.25 as I saw you have enabled HTTP/2 and thats one thing I have been waiting for. If making it work on 4.2.2 is a lot of work just say and I will just have to wait until I am able to upgrade the server.

I developed a temporary solution by using Node as a webserver proxy layer which I developed that uses HTTP/2 so I have apache running behind that and it is working well, so if it can't be compiled for 4.2.2 it isn't much of an issue.

[QNAP_Stephane]

it is a little headach to maintain x86 version, who will be EOL in some weeks (once 4.3 stable will be out )

moreover php 7.1 change API and required extension been reinstall in a new directory... the latest 4.3 version is a totally recompiled version with latest libs (dependency)

[QNAP_Stephane]

x64 version added

[Toxic17]

Stephane, will you be working on an ARM version too? just wanted to test this on my TS-121 running 4.3.2.0050.

[QNAP_Stephane]

Stephane, will you be working on an ARM version too? just wanted to test this on my TS-121 running 4.3.2.0050.

No ARMv5 is too old libc... a big headach with a lot of patch required

will be limited to ARM-x41 series (TS-x31P)

[Toxic17]

ok, thanks for the update

[raidforsaving]

it is a little headach to maintain x86 version, who will be EOL in some weeks (once 4.3 stable will be out )

moreover php 7.1 change API and required extension been reinstall in a new directory... the latest 4.3 version is a totally recompiled version with latest libs (dependency)

While I cannot understand the exact scale of maintenance concerns, I will say that it seems premature to drop support for x86, just because the x64 version is about to be released.

Just like the issues which occurred in the past 2 years with QTS, which caused many to delay upgrading due to serious stability concerns, it seems the impending x64/x86 qpkg debacle will be another reason for many to hold off on upgrading to 4.3. I'm not sure of the latest on this, so bear with me.

As this is a webserver app, with intent to host content directly over the internet, it seems horribly dangerous to abandon, given it is already vulnerable and will remain so for many months, until the qpkg issues are addressed.

Presuming the qpkg issue isn't 100% resolved, I implore you to consider updating this app until 4.3 is a seamless migration.

[QNAP_Stephane]

the other reason is also external hosting on QnapClub Repo, i need to check if 4.2.2 qpkg can be maintained with the repo...

not sure it is feasible, because actual 4.3.x still looking at x86 files instead to been swap to x86_64 model... and could create big confusion

[raidforsaving]

the other reason is also external hosting on QnapClub Repo, i need to check if 4.2.2 qpkg can be maintained with the repo...

not sure it is feasible, because actual 4.3.x still looking at x86 files instead to been swap to x86_64 model... and could create big confusion

Thanks for the response. I just want to make sure you are considering the real world impact of the decisions.

I would also assume/hope that qnap supported x86 apps will continue to be updated for some time? for the same reasons I explained? especially if there are security issues.

[Toxic17]

While I cannot understand the exact scale of maintenance concerns, I will say that it seems premature to drop support for x86, just because the x64 version is about to be released.

Just like the issues which occurred in the past 2 years with QTS, which caused many to delay upgrading due to serious stability concerns, it seems the impending x64/x86 qpkg debacle will be another reason for many to hold off on upgrading to 4.3. I'm not sure of the latest on this, so bear with me.

Dont forget QNAP Stephane's own QPKGs are not official QNAP QPKG'sand he does this in his free time. he can stop support when he wants to.

[raidforsaving]

While I cannot understand the exact scale of maintenance concerns, I will say that it seems premature to drop support for x86, just because the x64 version is about to be released.

Just like the issues which occurred in the past 2 years with QTS, which caused many to delay upgrading due to serious stability concerns, it seems the impending x64/x86 qpkg debacle will be another reason for many to hold off on upgrading to 4.3. I'm not sure of the latest on this, so bear with me.

Dont forget QNAP Stephane's own QPKGs are not official QNAP QPKG'sand he does this in his free time. he can stop support when he wants to.

Which is a fair point. and I do appreciate their efforts.

I'm trying to get to a current version for a web app, but they are all vulnerable due to the web server, including my current version. I'm hoping this is my best option to have one in the next few months. I have no confidence in qnap sufficiently addressing the x64 migration concerns for several months.

[QNAP_Stephane]

thanks Toxic,

but my decision to stop or continue x86 (because i know some models like x39 will not survive to to 4.3.0, may be x59 as well not checked) depend also on how QnapClub can manage the repo

providing 4.2.2 and 4.3.x FW version... without to have to make 2 separate repo...

a bit complicated, all this transition....