Example: deliver the contents of a website
Send a build as a prepared state and switch to it deliberately afterwards.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs.
This example uses folder transfer with the release mode.
- On B, create a private alias such as
websiteand normal receive rights. - B sets up the folder policy for the mode you want. For prepared states use
--mode releaseand explicit--activatordevices. When changing a policy, state the complete rights you want; do not assume silent additions. - A builds the website locally or in CI and sends the immutable output folder with
--mode release. - Only after the verified tree receipt, read the current state with
release headand activate it deliberately. - Wait for the separate activation receipt. The application itself has to use the activated state; starting a process or restarting a service stays a job for your own operating environment.
Example for steps 3 to 5 after the full setup:
pipeit send ./dist --contents --mode release --profile v2 \
--target TARGET-DEVICE --destination website --json
pipeit release head --target TARGET-DEVICE --policy POLICY-ID
pipeit release activate TRANSFER-ID --target TARGET-DEVICE \
--policy POLICY-ID --expected-generation GENERATIONRelated guides
- Command line and servers
Store, update or activate a folder
Three receiving modes with different effects, and what none of them does.
- 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
A CI step with a verifiable result
Deliver a folder from a pipeline and let the exit code decide whether the next step may run.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.