DietPi
DietPi copied to clipboard
MichaIng
DietPi-Software | Pydio Cells
Pydio 8 is now at End of Life. It says here that arm compilation is on the roadmap 2020 Q1.
Just want to open an issue here to keep track. Thanks for the awesome work!
@chunjiw Many thanks for heads up. Hmm they mention ARM 64bit support explicitly, I hope ARMv6/7 will be supported as well. Having webserver and everything included has the huge disadvantage that binaries need to be compiled at all instead of simply downloading html/PHP code to run on any desired webserver. But of course we cannot support officially EOL marked web application software for long.
EDIT: Or we build the binary with Go environment: https://github.com/pydio/cells#installing
Pre-compiled binaries are still available for x86_64 only 😞: https://download.pydio.com/pub/cells/release/3.0.3/
Latest dev and nightly builds are however available for aarch64 as well (since 2022), so probably this is true for next release as well: https://download.pydio.com/pub/cells/nightly/2022-01-16/
Still not sure what to do about ARMv6/7 then, of course compiling can be tested. Since especially on ARMv6 this will likely take a lot of time, we may provide pre-compiled binaries on our own server.
Pydio Cells seems to have an import tool to import from a running Pydio 8 instance: https://pydio.com/en/pydio-cells/why-migrating-pydio-8-cells
So we can provide migration steps.
Install instructions: https://pydio.com/en/docs/kb/deployment/install-cells-raspberry
Related forum topic: https://dietpi.com/forum/t/pydio-8-php-desktop-client-for-linux/16774
@MichaIng I guess we need to remove Pydio (ID 48) from our repository as it is not working on Bookworm anymore. Last version has been released 3 years ago. If you agree, I will open PR to remove Pydio.
How does it not work anymore? Does it not support PHP 8.2? ... this one seems to indicate the same: #5171
I wonder whether we should implement Pydio Cells as direct replacement and offer a migration for all users.
based on a forum post, I tested all 3 Webserver. On Apache our old config file is leading to a service failure. For the other 2 web server, I received a HTTP 500.
Oh right, that php_admin_value works with mod_php only, not with PHP-FPM. So we would need to add a PHP config instead to set "output_buffering Off". However, the internal server error indicates an issue with PHP. Could be checked with
journalctl -u php8.2-fpm
I hope errors are passed through.
there is nothing within php8.2-fpm service log, but I found something within Nginx error.log (best to open with N++)
AFAICS these are all deprecation warnings, hence visual only. But probably they are indirectly the reason:
2024/01/23 21:20:02 [error] 21764#21764: *1 upstream sent too big header while reading response header from upstream, client: 192.168.0.93, server: dietpizpi3, request: "GET /pydio/ HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "192.168.0.23"
Probably the deprecation warnings are send via header and are too large/many 😄. However, does not make sense to investigate further. Since there has been no work for years on Pydio 8, we should just remove it, or better replace with Pydio Cells ASAP. I'll at least disable it for Bookworm/Trixie for now.