Run sternway-cli commands

You need sternway-cli on your PATH and a token with the right scopes (Set up the command line).

Pass the token

Pass the token in STERNWAY_TOKEN, or in a chmod 600 file named with --token-file. It’s never read from the command line, where other users and your shell history would see it.

Run commands

export STERNWAY_TOKEN=stw_…
sternway-cli whoami                       # the token's name, scopes and expiry
sternway-cli hosts                        # label, address and id of each host
sternway-cli connect web-1                # opens a terminal to web-1 in the app
sternway-cli run uptime --hosts web-1,web-2
sternway-cli run deploy --hosts web-1 --var tag=v1.4 --json
sternway-cli cp web-1:/etc/os-release .
sternway-cli cp ./build.tar web-1:/srv/releases/ --overwrite

• Name a host or snippet by its label (case is ignored if there’s no exact match) or by id. Use the id when two hosts share a label.
• run runs command snippets only, filling {{$HOST}} and the other built-ins per host like Run on hosts › Collect results, and shows in the app.
• cp copies one file into a folder, and only replaces a file with --overwrite.
• --json prints JSON for scripts.
• hosts skips a team’s hosts when it blocks unencrypted exports, and says on stderr how many.

run and cp aren’t recorded in session recordings or logs.

The exit statuses tell a script what went wrong.

Every command and option: sternway-cli reference.