view doc/jp/file_share_configuration.rst @ 3403:404d4b29de52

plugin file, XEP-0234: registering is now done by class + use of async: - instead of registering a callback, a file sending manager now register itself and must implement some well known method (`fileSend`, `canHandleFileSend`) and optionally a `name` attribute - `utils.asDeferred` is now used for callbacks, so all type of methods including coroutines can be used. - feature checking is now handled by `canHandleFileSend` method instead of simple namespace check, this allows to use a method when namespace can't be checked (this is the case when a file is sent to a bare jid with jingle)
author Goffi <goffi@goffi.org>
date Thu, 12 Nov 2020 14:53:15 +0100
parents 7ebda4b54170
children
line wrap: on
line source

.. _jp-file_share_configuration:

=========================================================
file/share/configuration: file sharing node configuration
=========================================================

``configuration`` commands are use to check or modify settings of a file sharing node.
This is not standard and specific to SàT file sharing component.

The configuration is similar as pubsub one.

Only ``access_model`` can be used so far, with the ``open`` or ``whitelist`` values.


get
===

Retrieve file sharing node configuration.

example
-------

Get configuration of a file sharing node::

  $ jp file share configuration get -P "/some/path" louise@files.example.org

set
===

Set configuration of a file sharing node.

example
-------

Make a repository public::

  $ jp file share configuration set -c files.example.net -P "/public_files" -f
  access_model open