gDown Installation

gDown installs alone, on one machine or as a cluster, with one script. The script only verifies then installs: it checks a signed manifest (Ed25519) and the SHA-256 of the binary before anything is written.

gDown becomes a systemd service (user gluonify-gdown, data in /var/lib/gluonify-gdown). A first node starts a new cluster of one; the generated administrator password is kept in a file readable by root only.

Run the first command on the first machine. Its cluster token is in /etc/gluonify-gdown/gdown.env (GRAPH_AUTH_TOKEN): copy it, then run the last command on each other machine, with --seed pointing to the first node. The token goes through the environment, never as an argument. The new member configures itself from the seed and joins. Three members keep working when one is lost.

Options

  • --node-id: name of the member (default: the host name).
  • --advertise-host: the address the other members use to reach this one (default: the host name).
  • --seed: URL of a member of an existing cluster; leave it out on the first node.
  • --data-dir: data directory (default /var/lib/gluonify-gdown).
  • --version: release to install (default: the latest).
  • --key-sha256: fingerprint of the release key; the script refuses any other key.

Ports

8080 (HTTP: API, web console), 7687 (Bolt) and 9000 (Raft, between members only). Open 9000 between the machines of a cluster, and nothing more than 8080 and 7687 for your clients.