Mercurial > libervia-backend
view doc/libervia-cli/appication.rst @ 4081:84f6bee6440d
installation: moved from `setup.py` to `pyproject.toml`:
- updated installation to use the now standard `pyproject.toml` instead of legacy
`setup.py`. `setup.py` and other legacy files have been deleted.
- removed outdated README4PACKAGERS
- removed pylintrc which has not been correctly reviewed. Linter conf should go to
`pyproject.toml` now.
- [hatch](https://hatch.pypa.io) is now used as main building tool. However, thanks to the
use of standards, other tools can be used too.
- update .hgignore
- several dependencies version bump, with code update to adapt to changes.
author | Goffi <goffi@goffi.org> |
---|---|
date | Tue, 06 Jun 2023 16:45:16 +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