Mercurial > libervia-backend
view doc/libervia-cli/pipe.rst @ 3904:0aa7023dcd08
component AP gateway: events:
- XMPP Events <=> AP Events conversion
- `Join`/`Leave` activities are converted to RSVP attachments and vice versa
- fix caching/notification on item published on a virtual pubsub node
- add Ad-Hoc command to convert XMPP Jid/Node to virtual AP Account
- handle `Update` activity
- on `convertAndPostItems`, `Update` activity is used instead of `Create` if a version of
the item is already present in cache
- `events` field is added to actor data (and to `endpoints`), it links the `outbox` of the
actor mapping the same JID with the Events node (i.e. it links to the Events node of the
entity)
- fix subscription to nodes which are not the microblog one
rel 372
author | Goffi <goffi@goffi.org> |
---|---|
date | Thu, 22 Sep 2022 00:01:41 +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