Mercurial > libervia-backend
view doc/libervia-cli/appication.rst @ 3888:aa7197b67c26
component AP gateway: AP <=> XMPP reactions conversions:
- Pubsub Attachments plugin has been renamed to XEP-0470 following publication
- XEP-0470 has been updated to follow 0.2 changes
- AP reactions (as implemented in Pleroma) are converted to XEP-0470
- XEP-0470 events are converted to AP reactions (again, using "EmojiReact" from Pleroma)
- AP activities related to attachments (like/reactions) are cached in Libervia because
it's not possible to retrieve them from Pleroma instances once they have been emitted
(doing an HTTP get on their ID returns a 404). For now those cache are not flushed, this
should be improved in the future.
- `sharedInbox` is used when available. Pleroma returns a 500 HTTP error when ``to`` or
``cc`` are used in a direct inbox.
- reactions and like are not currently used for direct messages, because they can't be
emitted from Pleroma in this case, thus there is no point in implementing them for the
moment.
rel 371
author | Goffi <goffi@goffi.org> |
---|---|
date | Wed, 31 Aug 2022 17:07:03 +0200 |
parents | 267e4987b58b |
children |
line wrap: on
line source
============================================= application: external applications management ============================================= Libervia can launch and manage external applications. This is useful to integrate external services, notably in the web frontend. The command can be used either with ``application`` or the shortcut ``app``. list ==== List available applications. This command can show either the list of available application (which could be launched) and/or the list of running application. By default both available and running application are shown, this can be filtered by using ``-f {available,running}, --filter {available,running}`` example ------- List available applications:: $ li app list -f available start ===== Start an application. Depending on the application and its availability locally, this make take some time (resources may have to be downloaded). example ------- Start Weblate:: $ li app start weblate .. _li_app_stop: stop ===== Stop an application. If several instances of the same application are running, ``-i ID, --id ID`` can be used to specify which one must be stopped. example ------- Stop Weblate:: $ li app stop weblate exposed ======= List exposed values from a running application. Exposed values may be the port used, passwords automatically generated, or fields useful for web integration. As for :ref:`li_app_stop`, if several instances of the same application are running, one can be specified using ``-i ID, --id ID``. example ------- Show exposed values of a running Weblate:: $ li account application exposed weblate