Extract the worker kit into its own repo (RigForge); keep a connection guide here#74
Merged
Merged
Conversation
…e here Executes the worker split (#71): the worker provisioning kit now lives in its own repository, github.com/p2pool-starter-stack/rigforge. This repo keeps just enough to connect miners to the orchestrator. - Remove worker/ (the kit moved to RigForge, with its script renamed rigforge.sh, a self-contained README, MIT LICENSE, .gitignore, and shellcheck CI). - Rewrite docs/workers.md → "Connecting Miners": a complete guide for people who already run XMRig (the 3333 endpoint, minimal config, multi-rig, mDNS, firewall, dashboard, and an explicit "any recent XMRig works — no required miner version" note), then point newcomers to RigForge to provision a tuned miner from scratch. - Repoint every worker-kit link (README, docs index, getting-started, hardware) to the RigForge repo; rename the "Adding Workers" nav to "Connecting Miners". - Drop the now-dead /worker/* entries from .gitignore. Miner-vs-stack-version compatibility: xmrig-proxy and P2Pool accept any Stratum miner that supports NiceHash (XMRig does so automatically behind a proxy), so the stack's pinned proxy (6.26.0) / p2pool (v4.15.1) versions don't dictate a worker version — documented in docs/workers.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
VijitSingh97
added a commit
that referenced
this pull request
Jun 4, 2026
The worker kit was extracted to the RigForge repo (#71/#74), but a stale worker/ dir can linger locally with miner runtime logs/state until that cutover is finished. It wasn't ignored, so `git add -A` would sweep in those (sometimes very large) files. Nothing under worker/ is tracked, so ignoring it is safe. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Executes the worker split proposed in #71. The worker provisioning kit now lives in its own repository — p2pool-starter-stack/rigforge — and this repo keeps just enough to connect miners to the orchestrator.
Why
As detailed in #71, the worker was never really part of this project's codebase — it's stock upstream XMRig plus setup scripts, on a different machine, with a different toolchain, coupled to the stack only by the
host:3333Stratum contract. This repo is the orchestrator; miners are separate.The new repo: RigForge
github.com/p2pool-starter-stack/rigforge(public, MIT) — "provision a hardware-tuned XMRig miner in one command."rigforge.sh(renamed fromp2pool-starter-worker.sh), templates,util/,systemd/.LICENSE(MIT),.gitignore, and a shellcheck CI workflow. Fixed two pre-existing shellcheck warnings (SC2046, SC2155) the parent never linted.What changes here
worker/(6 files, ~850 lines) — it lives in RigForge now.docs/workers.md→ "Connecting Miners": a complete guide for people who already run XMRig (the 3333 endpoint, minimal config, multiple rigs, mDNS, firewall, dashboard appearance, and an explicit "any recent XMRig works — no required miner version" note), then point newcomers to RigForge to provision a tuned miner from scratch./worker/*entries from.gitignore.Miner ↔ stack version compatibility (per your question)
Checked the proxy and p2pool: there's no required miner version.
xmrig-proxyis "compatible with any pool and any miner that supports NiceHash" (XMRig enables that automatically behind a proxy), and RandomX has shipped in XMRig since 5.0. So the stack's pinned xmrig-proxy 6.26.0 / p2pool v4.15.1 don't dictate a worker version — now documented indocs/workers.md.Closes #71.
🤖 Generated with Claude Code