how-tos · section Sign in

Scripts.

The script library, running scripts, their runs and onboarding rules.

Run a saved script
A script is text with {{variables}}. Run renders it per machine and sends it as an approved command.
Stop a script that is still running
Scripts › runs. Stop is on a row that is still going. The first press asks you to confirm. The second press stops it.
Show script runs that have finished
The status menu hides runs that are still going, or keeps only those. The runs themselves stay.
Search script runs
The search box looks through the script, the machine, who ran it, and any output. It only hides rows.
Answer what a script asks
A {{name}} in the command is a question at run time. You type it. The preview shows the command before anything is sent.
Say what a blank in a script may contain
Each {{name}} has a shape. A value outside that shape is refused before the command is sent.
Keep a script answer off the record
Tick secret on a question. The run history and the audit store bullets. The machine receives the real answer.
Let a script question be left blank
Clear required. The yellow schedule warning goes away. A night run can leave that blank empty.
Fill a script blank from the machine
Set the source to from the machine. The hub puts the hostname, the LAN address, or a group into the command.
Always send the same value in a script
Set the source to fixed and type the value. Every run uses it. Nobody is asked.
Find a script by what it is for
The library is grouped. The kind menu and the operating-system menu hide the rest.
Show scripts for one operating system
The operating-system menu hides the other shells. A script marked any OS stays in the list.
Search the script library
The search box looks through the name, the description, the tags, and the command. It only hides rows.
Tag a script so you can find it
Tags are words on the script, comma separated. The library search looks through them. They are not a machine group.
Add a script to the library
Company admins write the text. Operators run it. A variable is filled in per machine, and it cannot become a second command.
Let a script keep running for hours
Give it up to is minutes. Two is the start. Twelve hours is the longest. Closing the page does not stop it.
Keep a script on one machine
Belongs to can be the company, or only one machine. The others do not list it.
Change a script in the library
Edit opens the saved script. Save changes keeps the same row. A run that is already going is not rewritten.
Copy a script
Copy opens a new script from a library row. The original stays. It is not in the library until you press add to library.
Remove a script from the library
Delete takes the script out of the library. The first press asks you to confirm. A run that is already going is a different button.
Ask what a script run did
Ask on a run fills a question about that run. Send is still yours. The printed output stays untrusted.
Run a script on a schedule
A time and the days. It runs on machines that are online then. An offline machine is skipped.
Run a script on weekdays
Tick the schedule, then clear Saturday and Sunday. A machine that is offline at that minute is skipped.
Run a script in another timezone
The timezone box copies this console's clock. Replace it and 02:00 means 02:00 there. This shot does not save.
Choose scripts for a new machine
When a machine first comes online, a rule can prompt someone to run a script, or start it itself. Match the operating system and the machine type.