deploy(d-miner): version-controlled user-systemd units for sampler + notify engine - #576
Merged
Merged
Conversation
frstrtr
force-pushed
the
dashboard/d-miner-systemd-units
branch
from
June 28, 2026 01:02
6ee1098 to
49b9d3a
Compare
…notify engine
D-MINER.1 sampler and D-MINER.5 notify engine are built and KAT-locked but had
no reproducible deployment path: the sampler was hand-deployed as user-systemd
on the contabo prod node, the notify engine had none. Capture both as config-
driven user units so the pipeline is turn-on-able and per-node truthful.
deploy/systemd/:
* c2pool-miner-sampler.service long-running D-MINER.1 sampler
* c2pool-miner-rollup.{service,timer} nightly per-worker/day rollup (00:10)
* c2pool-miner-notify.{service,timer} D-MINER.5 engine run, every 5 min
* c2pool-miner-daily.{service,timer} daily-summary (08:00, after rollup)
* c2pool-miner.env.example + README.md per-node config, no hardcoded paths
All paths/URLs/SMTP live in ~/.config/c2pool/miner.env so each node points at
its own dashboard + DB + relay. Additive only; engine selftest still 15/15.
frstrtr
force-pushed
the
dashboard/d-miner-systemd-units
branch
from
July 2, 2026 05:57
49b9d3a to
04b4ed5
Compare
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.
What
Version-controlled user-systemd units for the D-MINER pipeline. The
D-MINER.1 presence sampler and D-MINER.5 notify engine are built and KAT-locked,
but had no reproducible deployment path — the sampler was hand-deployed on the
contabo prod node and the notify engine had none. This makes the pipeline
turn-on-able from the repo and keeps it per-node truthful.
deploy/systemd/:c2pool-miner-sampler.service— long-running D-MINER.1 samplerc2pool-miner-rollup.{service,timer}— nightly per-worker/day rollup (00:10)c2pool-miner-notify.{service,timer}— D-MINER.5 enginerun, every 5 minc2pool-miner-daily.{service,timer}— daily-summary (08:00, after rollup)c2pool-miner.env.example+README.md— per-node config + install stepsWhy per-node honest
Every path, /local_stats URL, and SMTP/transport setting lives in
~/.config/c2pool/miner.env; nothing is baked into the units, so each nodepoints at its own dashboard + DB + relay (charter: per-node truthful, config-
driven not hardcoded).
Safety
Additive only — no script or consensus code touched. Units validate clean with
systemd-analyze verify; engine selftest still 15/15. The notify timer runsrunevery 5 min, safe against the 15-min offline-min default + hourly throttle.Notes
engine adapter later with no unit change.