mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-02 17:59:36 +07:00
@@ -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
|
||||
@@ -70,7 +70,7 @@ can be regenerated with a button in the GUI.
|
||||
After generating your keys, you need to copy your new public key to the
|
||||
destination server to ``.ssh/authorized_keys``.
|
||||
|
||||
See :doc:`sftp.rst` for additional information on how to set up certificate based authentication on SFTP.
|
||||
See :doc:`./sftp` for additional information on how to set up certificate based authentication on SFTP.
|
||||
|
||||
.. figure:: images/auth_rsa.png
|
||||
:alt: Form on admin page for generating RSA keys.
|
||||
|
||||
@@ -77,7 +77,7 @@ forcing them.
|
||||
<https://github.com/owncloud/core/issues/7009>`_ for discussion of this.
|
||||
|
||||
.. note:: There are more sharing options on config.php level available:
|
||||
:ref:`Configuration Parameters<configPHP_Sharing>`
|
||||
`Configuration Parameters <https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#sharing>`_
|
||||
|
||||
.. _transfer_userfiles_label:
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ If you get a result, the module is present.
|
||||
|
||||
Required:
|
||||
|
||||
* PHP (see :doc:`./system_requirements.rst` for a list of supported versions)
|
||||
* PHP (see :doc:`./system_requirements` for a list of supported versions)
|
||||
* PHP module ctype
|
||||
* PHP module curl
|
||||
* PHP module dom
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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<Bootstrapping>`.
|
||||
The ``MyResourceProvider`` class needs to be registered during the :ref:`app bootstrap<Bootstrapping>`.
|
||||
|
||||
.. 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
|
||||
@@ -181,6 +181,8 @@ we can simply dispatch it when we render our main page template.
|
||||
|
||||
.. code-block:: php
|
||||
|
||||
<?php
|
||||
|
||||
class MyController extends Controller {
|
||||
private IEventDispatcher $eventDispatcher;
|
||||
|
||||
@@ -196,9 +198,9 @@ we can simply dispatch it when we render our main page template.
|
||||
}
|
||||
|
||||
|
||||
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::
|
||||
|
||||
<template>
|
||||
<div>
|
||||
|
||||
@@ -3,7 +3,7 @@ Synchronizing with Thunderbird
|
||||
==============================
|
||||
|
||||
`Thunderbird <https://www.thunderbird.net>`_ is a feature-rich and mature mail client that can be turned into a full-fledged PIM. Since version 102, it supports address book synchronisation via CardDAV and automatic discovering calendars and address books available on the server.
|
||||
|
||||
|
||||
|
||||
Recommended method
|
||||
------------------
|
||||
@@ -33,7 +33,7 @@ Same thing here, if you lately want to add more calendar just redo the procedure
|
||||
|
||||
|
||||
Alternative: using the TbSync addon
|
||||
-------------
|
||||
-----------------------------------
|
||||
|
||||
For this method, you need to have two add-ons installed:
|
||||
|
||||
@@ -54,7 +54,7 @@ When they are installed, if you are on Windows, go to **Extras**/**Synchronisati
|
||||
Alternative: Using the CardBook add-on (Contacts only)
|
||||
------------------------------------------------------
|
||||
`CardBook <https://addons.thunderbird.net/en/thunderbird/addon/cardbook/>`_ is an advanced alternative to Thunderbird's address book, which supports CardDAV. You can have TbSync and CardBook installed in parallel.
|
||||
|
||||
|
||||
1. Click the CardBook icon in the upper right corner of Thunderbird:
|
||||
|
||||
.. image:: ../images/cardbook_icon.png
|
||||
|
||||
Reference in New Issue
Block a user