Skip to content

v0.1.2

Choose a tag to compare

@joshdaugherty joshdaugherty released this 20 Oct 17:40
cce1a1c

Documentation for adopting fleet-kit (#16, PR #18). No code changes.

  • README: what fleet-kit is for and who uses it, a "What's verified" table of everything not yet run live, and the install model. You install the package and keep your configuration in a private repository of your own, never a fork. A fork of a public repository has to stay public.
  • docs/getting-started.md: the operator's path from start to finish:
    • prerequisites, linking to robot-council/cli's setup;
    • install;
    • the private configuration repository, and what must never go in it;
    • FLEET_KIT_CONFIG;
    • seat-stage check, then --dry-run, then a first stage;
    • seat-pace pace, then read, then a scheduler;
    • updating.
  • docs/coordinators.md:
    • who does what;
    • getting the verdict through the log or on_change;
    • writing a pacing policy;
    • what a restart does to seats and their tasks;
    • an adoption checklist for a new organization.
  • Stale text fixed: the Windows Task Scheduler template no longer says read is unsupported on Windows. The scheduler examples and examples/seats.toml now assume a Composer install and a private config repository.