Add configurations sections to CORE - #25
Conversation
qlpqlp
commented
Mar 8, 2026
qlpqlp
commented
- Add configurations sections: Node Features, RPC, Network, ZMQ, Advanced
- Implement dynamic configuration handling in pup.nix script
- Enable Transaction Index, RPC Server, ZMQ, and Advanced options configurability
- Hard disable wallet (disableWallet = true) with no enable option
- Simplify exposes section by removing redundant rpc-tcp entry
- Update version to 0.0.11
- Update pup.nix hash to ZRyZ1ecKKRe0+UR5Jaq6kazke9/nJvL9yS1i4F5ajak=
- Add note about disabling/re-enabling pup after configuration changes"
- Add configurations sections: Node Features, RPC, Network, ZMQ, Advanced - Implement dynamic configuration handling in pup.nix script - Enable Transaction Index, RPC Server, ZMQ, and Advanced options configurability - Hard disable wallet (disableWallet = true) with no enable option - Simplify exposes section by removing redundant rpc-tcp entry - Update version to 0.0.11 - Update pup.nix hash to ZRyZ1ecKKRe0+UR5Jaq6kazke9/nJvL9yS1i4F5ajak= - Add note about disabling/re-enabling pup after configuration changes"
| "core-rpc" | ||
| ], | ||
| "listenOnHost": false | ||
| "listenOnHost": true |
There was a problem hiding this comment.
I think instead of hardcoding this to true we need to be able to template this file with some of the configuration options selected. This is a much larger change, but our goal is to allow multiple core instances to run side-by-side for comparison, and this will break that.
| "logoPath": "logo.png", | ||
| "shortDescription": "Run a full core node on your dogebox", | ||
| "longDescription": "This pup launches and configures a full Dogecoin Core node on your dogebox, allowing you to sync the blockchain and contribute to the network.", | ||
| "longDescription": "This pup launches and configures a full Dogecoin Core node on your dogebox, allowing you to sync the blockchain and contribute to the network.\n\nIMPORTANT: After saving configuration changes, you must DISABLE and then ENABLE the CORE pup to apply the new settings.", |
There was a problem hiding this comment.
We can probably define a restartCommand or something in the nix build section of the manifest that we trigger when a configuration option changes. Or maybe something as simple as sending a SIGHUP to the running process.
|
|
||
| echo "$RPCUSER" > /storage/rpcuser.txt | ||
| echo "$RPCPASS" > /storage/rpcpassword.txt | ||
| # RPC Configuration (from manifest config or defaults) |
There was a problem hiding this comment.
This is a much larger file now - we should pull it out into core/start.sh or something and read it off disk from pup.nix so we get all the fancy syntax highlighting etc
SomeoneWeird
left a comment
SomeoneWeird
left a comment
There was a problem hiding this comment.
I've left a few comments, this is good progress but I don't think should be merged in as-is
2 participants
