Merge branch 'master' into Documentation

Author: Brijeshthummar02

admin_manual/configuration_server/config_sample_php_parameters.rst

@@ -549,6 +549,18 @@ davstorage.request_timeout
 
 The timeout in seconds for requests to servers made by the DAV component (e.g., needed for federated shares).
 
+carddav_sync_request_timeout
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+::
+
+	'carddav_sync_request_timeout' => 30,
+
+The timeout in seconds for synchronizing address books, e.g. federated system address books (as run by `occ federation:sync-addressbooks`).
+
+Defaults to ``30`` seconds
+
 session_relaxed_expiry
 ^^^^^^^^^^^^^^^^^^^^^^
 
@@ -639,6 +651,22 @@ Disabling this is discouraged for security reasons.
 
 Defaults to ``true``
 
+auth.bruteforce.protection.force.database
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+::
+
+	'auth.bruteforce.protection.force.database' => false,
+
+Whether the brute force protection should write into the database even when a memory cache is available
+
+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.
+
+Defaults to ``false``
+
 auth.bruteforce.protection.testing
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -3714,6 +3742,36 @@ This is used to find external binaries like libreoffice, sendmail, ffmpeg and mo
 
 Defaults to ``['/usr/local/sbin','/usr/local/bin','/usr/sbin','/usr/bin','/sbin','/bin','/opt/bin']``
 
+files.chunked_upload.max_size
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+::
+
+	'files.chunked_upload.max_size' => 100 * 1024 * 1024,
+
+The maximum chunk size to use for chunked uploads.
+
+A bigger chunk size results in higher throughput, but above 100 MiB there are only diminishing returns,
+while services like Cloudflare already limit to 100 MiB.
+
+Defaults to 100 MiB.
+
+files.chunked_upload.max_parallel_count
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+::
+
+	'files.chunked_upload.max_parallel_count' => 5,
+
+The maximum number of chunks uploaded in parallel during chunked uploads.
+
+A bigger count results in higher throughput, but will also consume more server workers,
+while the improvements diminish.
+
+Defaults to 5.
+
 .. ALL_OTHER_SECTIONS_END
 .. Generated content above. Don't change this.
 

admin_manual/configuration_server/email_configuration.rst

@@ -43,6 +43,7 @@ connect Nextcloud to a remote SMTP server:
 
     * STARTTLS cannot be enforced. It will be used automatically if the mail server supports it. The encryption type should be set to 'None/STARTTLS' in this case. See :ref:`here<TLSPeerVerification>` for an example on how to configure self signed certificates.
     * NTLM authentication for Microsoft Exchange is not supported by the new mailer library. Try using `basic authentication <https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/authentication-and-ews-in-exchange#basic-authentication>`_ instead.
+    * Outlook and Microsoft Exchange have discontinued support for Basic authentication. It is no longer possible to use their services as your default email handler.
 
 * Encryption type: None/STARTTLS or SSL
 

admin_manual/windmill_workflows/index.rst

@@ -20,7 +20,10 @@ Installation
 Selecting the right Workspace
 -----------------------------
 
-With Windmill installed as an ExApp, the first time one visits Windmill's web interface, make sure to select the right workspace on the first run: Only the pre-existing "nextcloud" workspace is hooked up to nextcloud's internal event system, all other workspaces will need manual webhook setups for each workflow.
+With Windmill installed as an ExApp, the first time one visits Windmill's web interface,
+make sure to select the right workspace on the first run:
+Only the pre-existing "nextcloud" workspace is hooked up to nextcloud's internal event system,
+all other workspaces will need manual webhook setups for each workflow.
 If the wrong workspace is selected on the first run, it is always possible to switch workspace later in the left sidebar.
 
 .. image:: images/windmill_initial_workspace_selection.png
@@ -34,7 +37,11 @@ If you wish to change to a different workspace at a later time, you can do so vi
 Building a workflow
 -------------------
 
-Each workflow in Windmill is a listener to a Nextcloud Webhook Event. If you are using the ExApp-packaged Windmill, it will automatically register webhooks for the workflows you build using the following mechanism. If you are not using the ExApp-packaged windmill install then you will have to register webhooks for your workflows manually via the webhook_listeners API: see https://docs.nextcloud.com/server/latest/developer_manual/_static/openapi.html#/operations/webhook_listeners-webhooks-index
+Each workflow in Windmill is a listener to a Nextcloud Webhook Event.
+If you are using the ExApp-packaged Windmill, it will automatically register webhooks for the workflows you build using the following mechanism.
+If you are not using the ExApp-packaged windmill install then you will have to register
+webhooks for your workflows manually via the webhook_listeners API:
+see https://docs.nextcloud.com/server/latest/developer_manual/_static/openapi.html#/operations/webhook_listeners-webhooks-index
 
 The magic listener script
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -52,32 +59,59 @@ Nextcloud Scripts
 -----------------
 
 Nextcloud makes available a variety of scripts to be used in Windmill for interfacing with Nextcloud apps. You can find them
-at https://hub.windmill.dev/integrations/nextcloud and https://hub.windmill.dev/integrations/nextcloud/approvals or in your windmill instance when selecting existing scripts for creating a new workflow.
+at https://hub.windmill.dev/integrations/nextcloud and https://hub.windmill.dev/integrations/nextcloud/approvals
+or in your windmill instance when selecting existing scripts for creating a new workflow.
+
+To synchronize the scripts with the ones provided by the Windmill hub,
+you can run a flow named "Synchronize Hub Resource types with instance" in the Windmill admin workspace.
+
+You can create your own Nextcloud-related scripts by taking one of the existing ones as example.
+In a script, when sending a request to Nextcloud, make sure that the ``EX-APP-ID`` header is set to ``flow``.
+
+All the scripts we provide have a set of common input parameters:
+
+* nextcloudResource: This should be set to the path of the Windmill resource that was automatically created and contains what is necessary to authenticate against Nextcloud with the AppAPI authentication method. For example "u/wapp_user/appapi_nextcloud". You can find this path by looking at the resource list in Windmill.
+* userId: This is the ID of the user you want the request to be authenticated as.
+* useAppApiAuth: This is a boolean to choose between using the AppAPI authentication or basic auth. More details in the next section.
 
 Authentication
 ~~~~~~~~~~~~~~
 
-All bricks have the option to use "AppAPI Authentication" or normal authentication using a Nextcloud resource in Windmill. When using normal authentication you will need to provide the correct password or app password of the user on behalf of whom you want to execute the script. When using "AppAPI Authentication" you can impersonate any Nextcloud user. This will only work when using the ExApp-packaged version of windmill.
+All bricks have the option to use "AppAPI Authentication" or normal authentication using a Nextcloud resource in Windmill.
+When using normal authentication you will need to provide the correct password or app password of the user
+on behalf of whom you want to execute the script. When using "AppAPI Authentication" you can impersonate any Nextcloud user.
+This will only work when using the ExApp-packaged version of windmill.
 
 Passing values between blocks
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 When specifying script inputs you can either fill the parameters with static values or make references to the workflow input and the previous workflow steps.
 
-In order to reference the workflow input, use the ``flow_input`` variable. For example, ``flow_input.event.form.hash`` will reference the hash of a form from a nextcloud Forms event.
+In order to reference the workflow input, use the ``flow_input`` variable.
+For example, ``flow_input.event.form.hash`` will reference the hash of a form from a nextcloud Forms event.
 
-Each step in a workflow is automatically assigned a letter identifier. In order to reference results from previous steps in your parameters, use the ``results`` variable with the id of the step to reference as a sub property. For example, use ``results.e.submission.answers`` to use the answers of of a form submission retrieved via the "Get form submission from Nextcloud Forms" script identified with the letter "e".
+Each step in a workflow is automatically assigned a letter identifier.
+In order to reference results from previous steps in your parameters, use the ``results`` variable with the id of the step
+to reference as a sub property. For example, use ``results.e.submission.answers`` to use the answers of of a form submission
+retrieved via the "Get form submission from Nextcloud Forms" script identified with the letter "e".
 
 Approval/Suspend steps
 ~~~~~~~~~~~~~~~~~~~~~~
 
-Windmill allows using so-called approval steps, which are essentially asynchronous scripts that wait for the call to an additional webhook URL. The most prominent use case for this are approval workflows where you get automated input from somewhere which needs to be approved by a human. Once the human approves or disapproves by triggering the webhook URL the workflow will resume.
+Windmill allows using so-called approval steps, which are essentially asynchronous scripts that wait for the call to an additional webhook URL.
+The most prominent use case for this are approval workflows where you get automated input from somewhere which needs to be approved by a human.
+Once the human approves or disapproves by triggering the webhook URL the workflow will resume.
 
-In order to turn a newly added step into an approval step, the workflow edit screen, select the script and in the bottom right pan, go in the "Advanced" tab, "Suspend" sub tab and check "Suspend/Approval/Prompt".
+In order to turn a newly added step into an approval step, the workflow edit screen,
+select the script and in the bottom right pan, go in the "Advanced" tab, "Suspend" sub tab and check "Suspend/Approval/Prompt".
 
 .. image:: images/windmill_approval_step_config.png
    :alt: Screenshot of the workspace edit screen to turn a normal step into an Approval step
 
-Using the scripts provided for Nextcloud, you can send approval links to the humans in charge of approving via Nextcloud Talk or a simple notification in Nextcloud. Of course, you may also use any of the other scripts for sending messages available in the Windmill hub.
+Using the scripts provided for Nextcloud, you can send approval links to the humans in charge of approving
+via Nextcloud Talk or a simple notification in Nextcloud.
+Of course, you may also use any of the other scripts for sending messages available in the Windmill hub.
 
-Windmill has a default approval user interface at a specific URL, but it is not very nice. We recommend using the `approve_links <https://apps.nextcloud.com/apps/approve_links>`_ app which allows creating a beautiful temporary approval page with a custom message and approve and disapprove buttons.
+Windmill has a default approval user interface at a specific URL, but it looks very technical.
+We recommend using the `approve_links <https://apps.nextcloud.com/apps/approve_links>`_ app
+which allows creating a beautiful temporary approval page with a custom message and approve and disapprove buttons.

user_manual/files/sharing.rst

@@ -61,6 +61,8 @@ For adjusting the acceptance setting, go to **Settings** > **Personal** > **Shar
 .. figure:: ../images/sharing_autoAcceptSetting.png
 
 
+.. warning:: If the owner renames a shared file or folder, the new name will not be reflected on the recipient's side. This is needed to prevent overwriting existing files or folders on the recipient's end.
+
 Others with access
 ------------------