Skip to content

Latest commit

 

History

History
36 lines (30 loc) · 3.34 KB

File metadata and controls

36 lines (30 loc) · 3.34 KB

Documentation

Everything you need to run, configure, and operate Pithead.

New here? Start with the Getting Started guide — it takes you from a fresh Ubuntu machine to a synced, mining stack in a handful of commands. The other guides go deeper on individual topics once you're up and running.

Guides

Guide What it covers
Getting Started Prerequisites, installation, first-run setup, and what to expect while the node syncs.
Hardware Requirements Minimum vs. recommended specs for the stack host — CPU, RAM, disk, network, OS — plus lighter-footprint options. (Miner hardware lives in RigForge.)
Configuration Every config.json key and default, applying changes safely, reusing an existing node via data directories, and connecting to a remote Monero node.
The Dashboard Sync Mode, the live operational view, and how to read every panel.
Connecting Miners Pointing any existing rig at the stack, plus RigForge for setting up new miners.
Architecture The nine services, how they fit together, the privacy model, and the algorithmic XvB switching engine.
Privacy & Network Egress Every connection the stack makes off-box — what's Tor-routed, what's clearnet today, and how to harden each path.
Operations & Maintenance The full pithead command reference, upgrades, backups, and troubleshooting.
Testing Strategy The four test tiers (unit → contract → fake-daemon mini-stack → live matrix), the full scenario catalog, and which tier proves each situation.
Testing Guide For developers: how to write and run tests, per-change recipes, conventions, and real-hardware gotchas.
Test Inventory Generated, exhaustive list of every test/scenario across all suites — the inventory of what's covered.
Integration Testing The end-to-end config-matrix suite that validates the stack against real Monero + Tari nodes — the blocking pre-release gate.
Releasing How Pithead is versioned and released — one product, one version, the VERSION source of truth, and the GHCR stage→promote pipeline.
Release / Validation Server Why end-to-end validation needs a dedicated server (and what GitHub Actions does free on every PR), how to provision and harden it, and the safe self-hosted-runner setup.
FAQ Common questions, plus why Pithead vs. doing it yourself or Gupax.

Quick links