Entware-ng is designed to co-exist with the firmware with as less interaction as possible, to prevent the firmware from mal-functioning. This also means that php installed in Entware-ng is not even detected by the firmware (and by stock packages).
If you want to use php7 to run owncloud, you'll have to use one of Entware-ng's webservers.
Danke Mijzelf
Das ist eine klare Aussage...
Also bleib mir nix anderes als ein webserver zu installieren.
Habe es mit "OpenMediaVault" (SD-Karte) versucht,war ok aber für dauerbetrieb :-/
Welchen "Webserver"kannst du mir für den NAS542 V5.21 empfehlen ??
und wann wird Entware 3.x für uns verfügbar sein ?.
Thanks Mijzelf
That's a clear statement ...
So stay with me nothing else than a webserver to install.
Did it with "OpenMediaVault" (SD card) tried, was ok but for continuous operation: - /
Which "web server" can you recommend me for the NAS542 V5.21 ??
and when will Entware 3.x be available for us?
The 542 has enough 'oemph' to run any webserver. The Entware repo contains the 3 'big ones', Apache, nginx and lighttpd. They will all do their job. I would choose for nginx, for no other reason than that it's the most modern one.
About Entware 3.x, what exactly do you mean? The naming of the various Entware versions is a mess. First there was Entware, then there was Entware-ng. Together with Entware-ng there was Entware 3, which was basically the same as Entware-ng, but targeting the 3.x kernel. (while Entware-ng targeted 2.6.32).
Now both Entware-ng and Entware 3 are superseded by, drumrolls, Entware.
And AFAIK your Entware-ng is automatically upgraded to Entware at install. That happens on fw5 devices. (Fortunately not on fw5 devices, they are not compatible)