Skip to content

feat: pullgate bootstrap makes the users and units, runs doctor and enables the units #49

Open

Description

@groupsky

Why

pullgate bootstrap (#31, PR #48) does the token, the pairing and the instances. Two of its steps need pullgate doctor (#28), which does not exist yet:

  • step 1: make the users, the directories and the units as the README says, with the same code that pullgate doctor uses to check them;
  • step 5: run pullgate doctor, and enable the units.

Today, after bootstrap, the owner still runs the README "setup" block before it and the systemctl enable lines after it. Also, doctor should warn when pullgate's own files (listener.toml, bot-token, the deploy key, the known hosts file, the instance mode) changed outside pullgate (DESIGN.md section 17).

Done when

  • pullgate bootstrap makes the users, directories and units (step 1), with tests, using the code of pullgate doctor.
  • pullgate bootstrap runs pullgate doctor and enables the units at the end (step 5); a failed doctor enables nothing (a test).
  • The install CI job runs bootstrap without the README "setup" block before it.
  • README "Install" is install.sh, then pullgate bootstrap; DESIGN.md section 17 is updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions