diff --git a/admin_manual/configuration_files/external_storage/auth_mechanisms.rst b/admin_manual/configuration_files/external_storage/auth_mechanisms.rst index c19fb0574..9aa17e166 100644 --- a/admin_manual/configuration_files/external_storage/auth_mechanisms.rst +++ b/admin_manual/configuration_files/external_storage/auth_mechanisms.rst @@ -33,7 +33,7 @@ setup of the mount point. The **Log-in credentials, save in session** mechanism uses the Nextcloud login credentials of the user to connect to the storage. These are not stored anywhere on the server, but rather in the user session, giving increased security. -This method has some important drawbacks, since Nextcloud has no access to the storage +This method has some important drawbacks, since Nextcloud has no access to the storage credentials and therefore cannot perform any background tasks on the storage: * Sharing is disabled diff --git a/admin_manual/office/example-docker.rst b/admin_manual/office/example-docker.rst index 7391c410a..53a3fef4a 100644 --- a/admin_manual/office/example-docker.rst +++ b/admin_manual/office/example-docker.rst @@ -40,9 +40,7 @@ On a recent Ubuntu or Debian this should be possible using: apt-get install apache2 a2enmod proxy proxy_wstunnel proxy_http ssl -Afterward, configure one VirtualHost properly to proxy the traffic. For security reason we recommend to use a subdomain such as office.example.com instead of running on the same domain. An example config can be found below: - -.. code-block:: apache2 +Afterward, configure one VirtualHost properly to proxy the traffic. For security reason we recommend to use a subdomain such as office.example.com instead of running on the same domain. An example config can be found below:: ######################################## # Reverse proxy for Collabora Online @@ -113,7 +111,7 @@ Update the docker image: List running docker containers: .. code-block:: bash - docker ps + docker ps Stop and remove the Collabora Online container with the container id of the running one: .. code-block:: bash diff --git a/developer_manual/digging_deeper/projects.rst b/developer_manual/digging_deeper/projects.rst index b47f16ef1..b79be9468 100644 --- a/developer_manual/digging_deeper/projects.rst +++ b/developer_manual/digging_deeper/projects.rst @@ -12,7 +12,7 @@ Register a resource provider Things like files, deck cards and talk rooms are called Resources in projects. In order to add your own resource type, we need to create a class implementing the -`OCP\Collaboration\Resources\IProvider` interface. +``OCP\Collaboration\Resources\IProvider`` interface. .. code-block:: php @@ -82,7 +82,7 @@ In order to add your own resource type, we need to create a class implementing t } -The `MyResourceProvider` class needs to be registered during the :ref:`app bootstrap`. +The ``MyResourceProvider`` class needs to be registered during the :ref:`app bootstrap`. .. code-block:: php @@ -128,14 +128,14 @@ As you can see we also already register a front-end script, which we are going t Provide a user interface ------------------------ -The user interface can be registered through the public `OCP.Collaboration.registerType` +The user interface can be registered through the public ``OCP.Collaboration.registerType`` JavaScript method. The first parameter represents the resource type that has already -been specified in the `IResourceProvider` implementation. The second parameter is an object with +been specified in the ``IResourceProvider`` implementation. The second parameter is an object with three properties: - * `typeString` A localized string that will be displayed in the dropdown when choosing which resource type to link to - * `typeIconClass` A CSS class of the icon that should be used for this entry - * `action` An async function that will produce a resource picker UI and resolves with the resource id + * ``typeString`` A localized string that will be displayed in the dropdown when choosing which resource type to link to + * ``typeIconClass`` A CSS class of the icon that should be used for this entry + * ``action`` An async function that will produce a resource picker UI and resolves with the resource id The following example shows how a Vue.js component could be used to render the widget user interface, however this approach works for any other framework as well @@ -182,9 +182,9 @@ we can simply dispatch it when we render our main page template. \OC::$server->getEventDispatcher()->dispatch('\OCP\Collaboration\Resources::loadAdditionalScripts'); -In our Vue app, we can then render the pre-built projects picker available in the npm package `nextcloud-vue-collections`. +In our Vue app, we can then render the pre-built projects picker available in the npm package ``nextcloud-vue-collections``. -.. code-block:: vue +.. code-block::