docs: update desktop configuration branch from master

Signed-off-by: Rello <github@scherello.de>

Assisted-by: Codex:GPT-5

Author: Rello

admin_manual/configuration_database/mysql_4byte_support.rst

@@ -1,26 +1,29 @@
-=====================================
-Enabling MySQL/MariaDB 4-byte support
-=====================================
+===========================================
+Enabling MySQL/MariaDB full Unicode support
+===========================================
 
 .. note::
 
-    Be sure to backup your database before performing this database upgrade.
+    Be sure to back up your database before performing this database upgrade.
 
-In order to use Emojis (textbased smilies) on your Nextcloud server with a MySQL database, the
-installation needs to be tweaked a bit.
+To store the full range of Unicode characters in Nextcloud, including emoji,
+less-common writing systems, historic scripts, and specialized symbols, a
+MySQL or MariaDB database must use the ``utf8mb4`` character set. The older
+three-byte ``utf8`` character set cannot store characters outside `Unicode's
+Basic Multilingual Plane <https://en.wikipedia.org/wiki/Plane_(Unicode)>`_.
 
 .. warning::
 
     This guide applies only to MySQL 8 or newer and MariaDB 10.6 or newer.
     For a list of supported MySQL and MariaDB versions, see our
     :doc:`system requirements documentation <../installation/system_requirements>`.
 
-1. Make sure the following InnoDB settings are set on your MySQL server::
+1. Make sure the following InnoDB setting is enabled on your database server::
 
     [mysqld]
     innodb_file_per_table=1
 
-2. Restart the MySQL server in case you changed the configuration in step 1.
+2. Restart the database server if you changed the configuration in step 1.
 
 You can then verify that the change worked:
 
@@ -38,35 +41,50 @@ The result should look like this::
     +-----------------------+-------+
     1 row in set (0.00 sec)
 
-3. Open a shell, change dir (adjust ``/var/www/nextcloud`` to your nextcloud location if needed), and put your nextcloud instance in maintenance mode, if it isn't already::
+3. Open a shell, change to the Nextcloud installation directory (adjust
+   ``/var/www/nextcloud`` as needed), and enable maintenance mode if it is not
+   already enabled::
 
    $ cd /var/www/nextcloud
    $ sudo -E -u www-data php occ maintenance:mode --on
 
-4. Change your databases character set and collation:
+4. Change the database character set to ``utf8mb4`` and set its default
+   collation:
 
 .. code-block:: sql
 
     ALTER DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
 
-5. Set the ``mysql.utf8mb4`` config to true in your config.php::
+.. note::
+
+    The character set determines which characters can be stored. The collation
+    determines how text is compared and sorted.
+
+5. Enable ``utf8mb4`` support in the Nextcloud system configuration::
 
     $ sudo -E -u www-data php occ config:system:set mysql.utf8mb4 --type boolean --value="true"
 
-6. Convert all existing tables to the new collation by running the repair step::
+6. Run the repair command to convert the existing tables to the ``utf8mb4``
+   character set and collation::
 
     $ sudo -E -u www-data php occ maintenance:repair
 
 .. note::
 
-    This will also change the `ROW_FORMAT` to `DYNAMIC` for your tables.
+    This also changes the ``ROW_FORMAT`` of all tables to ``DYNAMIC``.
 
 7. Disable maintenance mode::
 
    $ sudo -E -u www-data php occ maintenance:mode --off
 
 Now you should be able to use Emojis in your file names, calendar events, comments and many more.
+Nextcloud can now use the full range of Unicode characters - such as emojis - in file names,
+calendar events, and comments.
 
 .. note::
 
-    Also make sure your backup strategy still work. If you use ``mysqldump`` make sure to add the ``--default-character-set=utf8mb4`` option. Otherwise your backups are broken and restoring them will result in ``?`` instead of the emojis, making files inaccessible.
+    Make sure your backup strategy supports ``utf8mb4``. If you use
+    ``mysqldump``, add the ``--default-character-set=utf8mb4`` option.
+    Otherwise, four-byte Unicode characters may not be preserved correctly
+    when the backup is restored. (A common symptom of this problem is the
+    appearance of ``?`` instead of emojis in text and file names).

admin_manual/configuration_files/previews_configuration.rst

@@ -31,6 +31,19 @@ and ``OC\Preview\MSOfficeDoc`` require LibreOffice. Image formats handled
 through ImageMagick, such as ``OC\Preview\Illustrator``, ``OC\Preview\SVG``
 and ``OC\Preview\TIFF``, require the corresponding ImageMagick support.
 
+Installing the ``imagick`` PHP extension is not on its own enough for those providers.
+ImageMagick also has to carry the delegate for the format, which is a separate build
+option and often a separate distribution package: ``OC\Preview\JP2`` needs the OpenJPEG
+delegate, and ``OC\Preview\HEIC`` and ``OC\Preview\AVIFImagick`` need an HEIF one,
+usually libheif. A provider whose delegate is missing is never registered, so those
+files keep their mimetype icon rather than producing a broken preview.
+
+``OC\Preview\AVIF`` is the one enabled-by-default provider with a build dependency of
+its own. It decodes with GD, which handles AVIF only if PHP was built against a libgd
+that supports it. Where it was not, enable ``OC\Preview\AVIFImagick`` alongside it:
+both answer for AVIF, GD is asked first, and ImageMagick is asked after it if GD
+returns nothing.
+
 Parameters
 ----------
 

admin_manual/webhook_listeners/budibase_workflows.rst

@@ -0,0 +1,39 @@
+==================
+Budibase workflows
+==================
+
+
+Budibase can easily be connected to Nextcloud and start automations reacting to Nextcloud events.
+
+
+Using a Nextcloud webhook as automation trigger
+-----------------------------------------------
+
+When creating a new automation in Budibase, you can choose "Webhook" as trigger.
+
+.. image:: images/new_automation.png
+   :alt: Budibase for creating a new automation, with highlighted "Webhook" button
+
+Budibase shows a schema request URL you can use to send the expected payload schema in advance.
+
+The easiest way to to this is to go to the Orchestration Gateway admin settings and click "Register new Budibase webhook":
+
+.. image:: images/new_budibase.png
+   :alt: Orchestration Gateway dialog for registering a Budibase webhook
+
+Here you can fill in the event you want your automation to be started by and the schema URL, and then send the schema. Budibase will show 4 detected bindings upon successful sending. You can then fill in the trigger URL provided by Budibase, all needed filters and the authentication tokens that should be included in the callback, and save.
+As soon as you have your automation deployed, it will now be triggered every time your chosen event happens in Nextcloud.
+
+
+
+Use payload information in bindings
+-----------------------------------
+
+For every event, there are 4 bindings registered in Budibase:
+
+* ``user``: the user that triggered the Nextcloud event
+* ``time``: a timestamp for the triggering
+* ``event``: an array containing additional information about the event (see the :ref:`list of webhook events<webhook_events>` for details)
+* ``authentication``: the requested authentication tokens
+
+These bindings can be used in any step of your automation to use the information given by the callback.

admin_manual/webhook_listeners/images/list_webhooks.png

@@ -36,17 +36,33 @@ Enable the ``webhook_listeners`` app that comes bundled with Nextcloud - e.g.
 
    occ app:enable webhook_listeners
 
-Listening to events
--------------------
+Managing webhooks
+-----------------
 
-You can use the OCS API to add webhooks for specific events. See:
+You can either use the OCS API to manage your webhooks or install the additional ``orchestration_gateway`` app to have a graphical user interface for adding, changing and deleting webhooks.
+
+the Orchestration Gateway adds an administration settings page listing your registered webhooks and making it easy to configure them.
+
+.. image:: images/list_webhooks.png
+   :alt: Orchestration Gateway settings showing a list of registered webhooks
+
+To add a new one, you can choose between a generic new webhook or a Budibase-specific one.
+
+
+.. image:: images/new_webhook.png
+   :alt: Orchestration Gateway dialog for adding a new webhook
+
+
+If you want to use the OCS API to add webhooks for specific events, see:
 `Register a new webhook <https://docs.nextcloud.com/server/latest/developer_manual/_static/openapi.html#/operations/webhook_listeners-webhooks-index>`_.
 
-Note: When authenticating with the OCS API to register webhooks, the account you
-use must have administrator rights or delegated administrator rights.
+.. note::
 
-Listing registered webhooks
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+  When authenticating with the OCS API to register webhooks, the account you use must have administrator rights or delegated administrator rights. To delegate the webhook registration to non-admin users, they have to be in a group that gets administration privileges for "Webhooks" granted. To use the Orchestration Gateway UI, they need *additional* privileges for "Orchestration Gateway".
+
+
+Listing registered webhooks via occ
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can list all currently registered webhook listeners from the command line:
 
@@ -203,6 +219,8 @@ The complete logs of the workers can be checked with (replace 1 with the worker
 
 It is recommended to restart this worker at least once a day to make sure code changes are effective and avoid memory leaks, in this example the service restarts every 60 seconds.
 
+.. _webhook_events:
+
 Nextcloud Webhook Events
 ------------------------
 
@@ -577,7 +595,104 @@ When the optional ``tables`` app is installed:
      "time": 1700054321,
    }
 
+
+Mail App Events
+~~~~~~~~~~~~~~~~~
+Mail events use different distinct payload formats, depending on the event.
+When the optional ``mail`` app is installed:
+
+- ``NewMessageReceivedEvent``
+
+.. code-block:: json
+
+   {
+     "event": {
+       "class": "OCA\\Mail\\Event\\NewMessageReceivedEvent",
+       "accountId": 34,
+       "inReplyToRfcMessageId": "5888857",
+       "mailboxId": 10,
+       "messageId": 108778,
+       "messageUri": "89789789",
+       "RfcMessageId": "897789",
+       "sentAt": "1787826765",
+       "subject": "Important data changes",
+       "threadRootId": "9947988"
+     },
+     "user": {
+       "uid": "carol",
+       "displayName": "Carol"
+     },
+     "time": 1787826832,
+   }
+
+
+- ``MessageSentEvent``
+
+.. code-block:: json
+
+   {
+     "event": {
+       "class": "OCA\\Mail\\Event\\MessageSentEvent",
+       "accountId": 34,
+       "inReplyToRfcMessageId": "5888857",
+       "sendAt": "1787826765",
+       "subject": "Important data changes"
+     },
+     "user": {
+       "uid": "carol",
+       "displayName": "Carol"
+     },
+     "time": 1787826832,
+   }
+
+
+- ``MessageFlaggedEvent``
+
+.. code-block:: json
+
+   {
+     "event": {
+       "class": "OCA\\Mail\\Event\\MessageFlaggedEvent",
+       "accountId": 34,
+       "flag": "Spam",
+       "mailboxId": 10,
+       "messageId": 108778,
+       "set": true,
+       "uid": 897789
+     },
+     "user": {
+       "uid": "carol",
+       "displayName": "Carol"
+     },
+     "time": 1787826832,
+   }
+
+
+- ``MessageDeletedEvent``
+
+.. code-block:: json
+
+   {
+     "event": {
+       "class": "OCA\\Mail\\Event\\MessageDeletedEvent",
+       "accountId": 34,
+       "mailboxId": 10,
+       "uid": 108778
+     },
+     "user": {
+       "uid": "carol",
+       "displayName": "Carol"
+     },
+     "time": 1787826832,
+   }
+
 .. note::
 
    For filtering or automation, always check the actual payload you receive, as it matches
    the JSON examples above, not PHPDoc or internal PHP array type style.
+
+
+.. toctree::
+    :maxdepth: 2
+
+    budibase_workflows