Skip to main content

Fleet deployment

The model is built for fleets, thousands of hosts per client. One team key is the shared bootstrap for the whole fleet. Each host gets its own per-server key from the server after it registers, so you never distribute per-host secrets, and you never template per-host config, because the monitoring logic lives on the server.

The same one-liner everywhere​

Any configuration management tool just runs the same install command:

curl -fsSL https://get.wakora.io | bash -s -- --key <YOUR_TEAM_KEY>

Pass the team key from your secret store or an environment variable, not in plain text in shell history.

cloud-init​

#cloud-config
runcmd:
  - curl -fsSL https://get.wakora.io | bash -s -- --key <YOUR_TEAM_KEY>

Ansible​

- name: Install Wakora agent
  hosts: all
  become: true
  tasks:
    - name: Run installer
      shell: "curl -fsSL https://get.wakora.io | bash -s -- --key {{ wakora_team_key }}"
      args:
        creates: /etc/wakora

The creates: /etc/wakora guard makes the task idempotent, so re-running the playbook does not re-install.

Declarative install for golden images​

When you need to declare services and credentials at bootstrap (golden images, strict ordering), use the long form. It complements auto-discovery, it does not replace the server model: the flags declare what is on the host, the monitoring logic still arrives signed from the server.

curl -fsSL https://get.wakora.io | bash -s -- --key <YOUR_TEAM_KEY> \
  --os=ubuntu --nginx --redis --mysql --mysql-user=U --ssl --vhost=example.com

Do not pass secret values inline, they are visible in the process list. Feed them through stdin, an environment variable, or a file, or set them on the host with wakora secret set. See Secrets.

White-label note​

Under an agency white-label, the binary and the service are still named wakora. White-label rebrands the console and the customer-facing value, never the agent itself. The agent is the neutral open engine.

Native package​

Planned

A .deb package for apt-based fleets is planned, onboarded with the same team key. Today the canonical path on every platform is the one-line installer above.