view doc/libervia-cli/pipe.rst @ 3767:fd3fe346a14a

docker (backend-dev): move dbus unix socket: there seem to be a regression with Docker: the volume is not propagated anymore with pre-existing files when a unix socket is inside. This is the case in `backend-dev` with the D-Bus unix socket put in `/home/libervia/.local/share/libervia/dbus_socket`, when the volume is mounted at `/home/libervia/.local/share/libervia/`, resulting in hard to debug failures. To work around that, the socket is not put in the volume mount point anymore, and has been moved to `/home/libervia/.local/share/`
author Goffi <goffi@goffi.org>
date Fri, 13 May 2022 19:21:17 +0200
parents 267e4987b58b
children
line wrap: on
line source

==================================================
pipe: send/receive data stream through shell pipes
==================================================

``pipe`` commands allow you to send or receive data stream through a Unix shell pipe.
Libervia will create a network connection (using XMPP and Jingle) between you an your
contact.

in
==

Receive data stream. Data will be send to stdout, so it can be piped out or simply print
to the screen. You can specify bare jids of entities to accept stream for, by default all
streams are accepted.

example
-------

Receive a video stream, and redirect it to mpv_ so show the video::

  $ li pipe in | mpv -

.. _mpv: https://mpv.io/

out
===

Send data stream. Data comes from stdin, so you may use pipe in something or just write
some text.

The only expected argument is the full jid of the device where the stream must be piped
out.

example
-------

Send a video to louise::

 $ li pipe out louise@example.org/libervia.123 < some_video.webm

Send output from ``cal`` command to louise::

 $ cal | li pipe out louise@example.org/libervia.123