Send a folder or only its contents
Send a whole folder with or without its outer folder, including dotfiles and empty subfolders.
You need
A native receiver with normal receive release and a fitting folder policy. For an alias destination its release is needed too. The preparation on B is part of the guide; A cannot force unknown target paths.
On receiver B, in addition to the destination project that is already set up:
pipeit directory configure --destination project --sender SENDER-ID --mode inbox
pipeit directory listThe CLI checks the location under the actual service identity. For a system service use the same user and state configuration as for the receive setup.
On sender A, send the folder including its outer folder:
pipeit send ./project --target TARGET-DEVICE --destination project --profile v2Send only its complete contents:
pipeit send ./project --contents --target TARGET-DEVICE \
--destination project --profile v2In the second case dotfiles and empty subfolders belong to the transferred tree. A trailing slash does not change the meaning. ./project/* is expanded by the shell and often leaves out dotfiles, so it is not an equal substitute for --contents.
The target receives a verified tree according to its storage mode. An alias is no licence to overwrite arbitrary existing files in that directory. For deliberate updating or activating there are separate modes and rights; see Store, update or activate a folder.
Related guides
- Command line and servers
Does a folder have to be stored twice first?
The native folder stream builds no full archive, but the receiving side still needs space while it checks.
- Command line and servers
Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
- Apps and browser
Send a folder in the browser
Choose a folder, keep empty subfolders where the browser allows it and send it as a protected archive.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.