* resolves: https://github.com/nextcloud/documentation/issues/9574
Some clients like DAVx5 use chunked transfer encoding.
PHP-FPM does not support this[1] because it requires to comply with the
CGI standard - 20+ years old - which enforces a Content-Length header.
So we need to buffer the whole request until passing it to PHP-FPM.
Without this 0-byte files would be created on Nextcloud as PHP-FPM will
not only set content-length to 0 but also does not pass the body data
stream.
[1] https://bugs.php.net/bug.php?id=51191 and https://github.com/php/php-src/pull/7509
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Single Nextcloud instances have shown to use less than 2 MiB of the configured JIT buffer size, so that 8 MiB is sufficient by a large margin. Using any larger value pre-occupies the `opcache.memory_consumption` accurdingly and 128 MiB would hence fill its default 128 MiB completely, without any benefit.
The example JIT size is hence reduced to 8 MiB. Enabling JIT however has shown to raise overall OPcache usage by a larger amount than the configured JIT size, so that `opcache.memory_consumption` might still need to be raised in some cases. This information is added to the documentation: https://github.com/nextcloud/all-in-one/issues/2755#issuecomment-1591848523
Additionally, the info is added that JIT is currently supported on x86 platforms only.
Signed-off-by: MichaIng <micha@dietpi.com>
Nextcloud won't log failed login attempts in log levels > 2.
Added this to the documentation, and, while at it, improved the fail2ban guide in a few other places.
Fixes#12327.
Signed-off-by: tgoeg <39340276+tgoeg@users.noreply.github.com>
Since we changed branch to `main` we need to fix the documentation accordingly.
Ref: https://github.com/nextcloud/vm/issues/2652
Signed-off-by: Daniel Hansson <github@hanssonit.se>
Clarify which versions we are testing and thus can support:
* MySQL 8.0 LTS + 8.4 LTS
* MariaDB 10.6 LTS, 10.11 LTS and 11.4 LTS
* *(other databases unchanged)*
Co-authored-by: Joas Schilling <213943+nickvergessen@users.noreply.github.com>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
* various apps/features/configurations require more than the minimum so let's make it clearer that only meeting the minimum does come with trade-offs
* the built-in Updater requires PHP memory_limit (and/or available RAM) equal to the current size of the downloaded Archive package (see nextcloud/updater#505). Otherwise it will always fail on step 5 (integrity check). Let's mention that so people aren't surprised. They can of course do a manual update still.
Signed-off-by: Josh <josh.t.richards@gmail.com>