Mercurial > libervia-backend
view doc/libervia-cli/appication.rst @ 3913:944f51f9c2b4
core (xmpp): make `send` a blocking method, fix `sendMessageData` calls:
original `send` method is blocking, and it is used as such by Wokkel and thus can't be
changed to an async method easily. However, an Async method is necessary to have an async
trigger at the very end of the send workflow for end-to-end encryption. To workaround
that, `send` is an async method which call `a_send`, an async method which actually does
the sending. This way legacy method can still call `send` while `a_send` can be await
otherwise.
Fix calls to `sendMessageData`: the method now being an `async` one, `ensureDeferred` had
to be used in some calls.
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sat, 24 Sep 2022 16:31:39 +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