Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
| Mode | Effect | What does not happen |
|---|---|---|
inbox | Stores the fully verified tree | No blanket overwriting or deleting of other people’s files |
release | Prepares a new complete folder state for later activation | The active state is not switched yet |
update | Updates files one by one, atomically per file, and keeps additional files | No atomicity of the whole tree and no removal of old extras |
Scroll sideways to see the whole table.
release and update need a destination and matching receiver releases. The receiver decides the allowed modes, senders and activation devices. An activation device is a role of its own: sending alone does not allow switching.
Related guides
- Command line and servers
Example: deliver the contents of a website
Send a build as a prepared state and switch to it deliberately afterwards.
- Command line and servers
Remove old files you no longer need
Normal sending never deletes anything. For a managed set of files there are three separate, deliberate actions.
- Command line and servers
Send a folder or only its contents
Send a whole folder with or without its outer folder, including dotfiles and empty subfolders.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.