Skip to content

site: the gates page still says "one authority per deployment" #554

Description

@nathancrtr

What is wrong

The public site describes the topology as "one authority per deployment". Since #502 (PR #550) the rule is one engine per repository, with one gateline up process per machine as the supported topology. AGENTS.md, TOPOLOGY.md §3.1 and MULTI-REPO.md §8 were restated in that pull request. The site was left out of it on purpose.

Where

  • site/how-it-works/how-gates-keep-a-human-in-charge.html: the opening paragraph (line 30), the section heading and its first paragraph (lines 209-210), and the table of contents entry (line 352). The heading's id one-authority-per-deployment is an anchor other pages may link to.
  • deploy/fly.example.toml line 19: a comment reading "one machine, one clone, one authority". The hosted recipe still serves one repository, so this may be right as it stands. Check it against DEPLOY.md.
  • docs/TOPOLOGY.md line 34: "Every other property of the system assumes one authority per deployment." Check whether this sentence survived the restatement by intent.

Done when

The site page states the rule the way TOPOLOGY.md §3.1 does, and any link to the old anchor still resolves.

Part of #492.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions