Receiver B: create a named destination
Give a private folder on the receiver a short alias that senders can pick.
You need
Receiving and the service identity already set up as in Set up Linux as a permanent receiver. The absolute target folder must exist, be private and be accessible to the actual service user.
On B:
pipeit destinations add project \
--inbox /ABSOLUTE/private-folder \
--allow-sender SENDER-ID
pipeit destinations listFor a system service, run both commands as sudo -u pipeit pipeit … --state-dir /var/lib/pipeit as well. The CLI checks real read and write access, synchronization and the removal of its own test files before publishing. A successful test as administrator does not replace the check as the service user.
The sender sees the alias, not the private absolute path. If the state is pending, reconcile the same publication with pipeit destinations sync; do not create a second destination right away. An alias release does not replace the normal receive release.
Related guides
- Command line and servers
Sender A: choose the destination and send a file
Pick the receiver’s alias and send a large file with a receipt you can rely on.
- Command line and servers
Set up Linux as a permanent receiver
Let a server accept files from one named sender into a private inbox.
- Command line and servers
Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.