Run a Playbook

Update packages, install software, harden SSH or free disk space on one or many servers, with a dry run and a preflight check on each server.

Before you start: At least one connected server.

  1. 1

    Open Playbooks and choose a playbook

    Playbooks is under Automation in the sidebar, grouped by purpose. Each card lists the distributions it supports and when it last ran.

  2. 2

    Set the options

    Most playbooks have a few options, such as a PHP version and extensions, the services to restart, or how much of the journal to keep. Every option has a default.

  3. 3

    Choose the servers

    Select servers by name, group, tag or operating system, or choose all of them. The list below shows every server your selection includes and any known problem that would stop the playbook there, before any server is contacted.

  4. 4

    Choose how it rolls out

    Try one server first is on by default: one server runs the playbook, and the run waits for you before continuing. At a time sets the batch size, and Stop after sets how many failures to allow before no further batch starts.

  5. 5

    Dry run, then run

    Dry run reports what would change on every server without changing anything. When the results look right, choose Run. The run opens and shows each server’s preflight, steps and output as they happen.