miner/deploy/quantus-miner.sysusers.conf at 338b4a7d3215279986c8d2dede102afe488fe8a5 - miner - Gitea: Git with a cup of tea

blackbeard/miner

Files

rob thijssen b9e1d21ec9

ci / fmt (pull_request) Successful in 24s

Details

ci / clippy (pull_request) Successful in 1m38s

Details

ci / doc (pull_request) Successful in 2m0s

Details

ci / test (pull_request) Successful in 7m47s

Details

deploy: build on push to main and land the binary on the mining hosts

quantus/miner#8. The miner is now deployed from this repo, not from
lair/quantus's release-pinned workflow (lair/quantus#4 retires that half).

- .gitea/workflows/deploy.yaml: build on cuda-13.0 (Fedora 43 like the
  hosts, and the runner with nvcc for #3) with the commit embedded, then per
  host in the matrix: sudoers preflight against deploy/infra-setup.sh,
  credentials copied from the node, miner.env rendered with the node's mesh
  IP resolved on the miner host, checksum-gated push of binary and unit,
  scoped firewalld rule for the exporter, restart only on change. Validate
  asserts the unit is active, --version carries this commit, the miner sees
  the matrix's device count, and miner_hashes_total advances within 120 s.
  If validate fails after a restart, the previous binary is restored.
- deploy/: the unit, sysusers, firewalld service and env template moved
  verbatim from lair/quantus asset/, plus infra-setup.sh with the miner role
  (and two new cp grants for the rollback). Applied to benjy and quadbrat.
- Matrix: benjy and quadbrat; beast present but commented out per the
  operating policy in #1.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

2026-09-03 13:28:52 +03:00

5 lines

243 B

Plaintext

Raw Blame History

 #Type Name            ID  GECOS                           Home directory         Shell
 u     quantus-miner   -   "Quantus miner service account" /var/lib/quantus-miner /usr/sbin/nologin
 m     quantus-miner   video
 m     quantus-miner   render