These entries are currently hard-coded in the manual itself (on the config parameter page that is generated from this config sample file). This PR moves them to the proper place, the config sample file itself.
A separate PR in the docs repo will remove their hard-coded entry in the manual, but this is not dependent on that PR.
Signed-off-by: Josh <josh.t.richards@gmail.com>
When running nextcloud with a web hoster it might be necessary
to extend .user.ini after each update (e.g. adding memory_limit).
To automate this step, an additional config entry may be provided
in config.php that specifies the lines to be added to .user.ini.
If the config option 'user_ini_additional_lines' exists, the provided
value (string or array of strings) will be added to .user.ini.
Signed-off-by: Mathias Koehrer <koehrer08@koehrer-mail.de>
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
PR #51712 added new preview_ffprobe_path parameter. This PR updates config.sample.php to document this new optional parameter and the fallback behavior if the option is not set.
Signed-off-by: invario <67800603+invario@users.noreply.github.com>
Enable via:
./occ config:system:set core.login_flow_v2.allowed_user_agents 0 --value '/Custom Foo Client/i'
./occ config:system:set core.login_flow_v2.allowed_user_agents 1 --value '/Custom Bar Client/i'
if user agent string is unknown
the template with "Access forbidden"-"Please use original client" will be displayed
Signed-off-by: Misha M.-Kupriyanov <kupriyanov@strato.de>
When both `skeletondirectory` and `templatedirectory` are set to empty
strings in configuration, templates folder creation should be disabled
and no Create templates folder option should be present
in new folder menu.
Related: https://github.com/nextcloud/server/issues/39266
Related: https://github.com/nextcloud/server/issues/46455
Author-Change-Id: IB#1156403
Signed-off-by: Pawel Boguslawski <pawel.boguslawski@ib.pl>
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
== Goal
Allow disabling mail delivery altogether.
== Usecase
If mails ought to be send by other means than rendering messages from
templates and sending them via SMTP-like protocols.
Example: listening to specific Nextcloud events and pass parameters to
a centralized (i.e. REST-based) API that sends e-mails.
Signed-off-by: Thomas Lehmann <t.lehmann@strato.de>
Using the database is most likely worse for performance, but makes investigating
issues a lot easier as it's possible to look directly at the table to see all
logged remote addresses and actions.
Signed-off-by: Joas Schilling <coding@schilljs.com>
Big federated setups may need a longer timeout, which they now can
configure.
Signed-off-by: Pablo Zmdl <pablo@nextcloud.com>
Co-authored-by: Josh <josh.t.richards@gmail.com>
This feature is important for nextcloud running on
distributions like NixOS, where all the standard
search paths do not exist.
Also added tests.
This fixes issue #43922
Co-authored-by: Daniel <mail@danielkesselberg.de>
Signed-off-by: Reno Reckling <e-github@wthack.de>