Mercurial > libervia-backend
view doc/libervia-cli/file_share_configuration.rst @ 3998:402d31527af4
plugin app manager: `start` doesn't wait anymore for actual app start:
Application may be long to start (e.g. a Docker app may have to download images first,
and even without the downloading, the starting could be long), which may lead to UI
blocking or bridge time out.
To prevent that, `start` is now returning immediately, and 2 new signals are used to
indicate when the application is started, of if something wrong happened.
`start` now returns initial app data, including exposed data without the computed exposed
data. The computed data must be retrieved after the app has been started.
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sat, 04 Mar 2023 18:30:47 +0100 |
| parents | 267e4987b58b |
| children |
line wrap: on
line source
.. _libervia-cli_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 Libervia 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:: $ li file share configuration get -P "/some/path" louise@files.example.org set === Set configuration of a file sharing node. example ------- Make a repository public:: $ li file share configuration set -c files.example.net -P "/public_files" -f access_model open