Mercurial > libervia-backend
view doc/libervia-cli/remote-control.rst @ 4247:4aa62767f501
plugin app manager: various improvements:
- Generated password must now be named and are stored, so they are re-used on following
restarts. Password size can now be specified.
- New `not` filter for `!libervia_param` to inverse a boolean value.
- Former `front_url` field has been renamed to `web_url_path` as it is the URL path used
for web frontend. All Web frontend related field are prefixed with `web_`.
- `front_url` is now used to specify a whole front URL (notably useful if an app uses its
own domain). A list can be used to retrieve a key, like for `url_prefix`, and `https`
scheme is added if no scheme is specified.
- An abstract class is now used for App Managers.
- Last application start time is stored in persistent data.
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Fri, 31 May 2024 11:08:14 +0200 |
| parents | 05f01ac1d5b2 |
| children |
line wrap: on
line source
.. _libervia-cli_remote-control: ============================== remote-control: Remote Control ============================== The ``remote-control`` feature allows you to control another device or be controlled by another device. send ==== Send control events to another device. For now, it only sends keyboard events. example ------- Louise wants to control Pierre's device:: $ li remote-control send pierre@example.net receive ======= Use ``receive`` to establish a connection with another device and accept incoming control events. This feature uses the freedesktop.org's Remote Desktop portal, which must be installed on your system and compatible with your platform. On most Wayland-based desktop environments, this portal is usually available. Immediately upon connecting, Libervia CLI requests permission to initiate the remote control session, event if not request has been received yet. This ensures that the connection can be established without requiring manual intervention to authorize access. After a connection has been accepted and terminated, the command quits. ``--verbose, -v`` can be used to show received input events. If you don't expect to share screen, use ``S {yes,no,auto}, --share-screen {yes,no,auto}`` with a value of ``no``. example ------- Louise is expecting Piotr to control her device and wants to automatically accept control from him:: $ li remote-control receive louise@example.org