You can [build signal-cli](#building) yourself, or use
the [provided binary files](https://github.com/AsamK/signal-cli/releases/latest), which should work on Linux, macOS and
-Windows. For Arch Linux there is also a [package in AUR](https://aur.archlinux.org/packages/signal-cli/) and there is
-a [FreeBSD port](https://www.freshports.org/net-im/signal-cli) available as well.
+Windows. For Arch Linux there is also a [package in AUR](https://aur.archlinux.org/packages/signal-cli/), as well as
+a [FreeBSD port](https://www.freshports.org/net-im/signal-cli) and
+an [Alpine aport](https://pkgs.alpinelinux.org/packages?name=signal-cli).
System requirements:
- at least Java Runtime Environment (JRE) 17
- native library: libsignal-client
- The native libs are bundled for x86_64 Linux (with recent enough glibc, see #643), Windows and MacOS. For other systems/architectures
+ The native libs are bundled for x86_64 Linux (with recent enough glibc, see #643), Windows and MacOS. For other
+ systems/architectures
see: [Provide native lib for libsignal](https://github.com/AsamK/signal-cli/wiki/Provide-native-lib-for-libsignal)
### Install system-wide on Linux
* Pipe the message content from another process.
- uname -a | signal-cli -a ACCOUNT send RECIPIENT
+ uname -a | signal-cli -a ACCOUNT send --message-from-stdin RECIPIENT
* Receive messages