The rpcbind documentation on the example file should match the Manpage. Even more they have opposite meanings.
This should close #9272
Please fix the trailing whitespace on the lines you've modified.
Unfortunately this file isn't really maintained. Couldn't we remove the help texts and refer everyone to the manpages/bitcoind -help?
Also should close #9272
@fanquake I amended the commit with the fix. I agree with @MarcoFalke if the file is not maintained it should be refered to the Manpage, it is however usually expected from a standard Debian package to offer an example conf in /usr/share/doc.
I vaguely remember we had a script at some point that generated a sample bitcoin.conf from the option help, this would be more convenient than manually maintaining documentation in multiple places. No idea though. Didn't even know this file was shipped.
I tried looking for the script and could not find it. I am willing to make a new script to generate this file, is it ok to do it in python ?
Also there some sections in the sample conf with more details which are not in the Man, maybe they should moved the Man ?
On November 21, 2018 11:27:06 AM GMT+01:00, "Wladimir J. van der Laan" notifications@github.com wrote:
BTW this will change with #14532
-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/bitcoin/bitcoin/pull/14740#issuecomment-440612921
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
67 | -# This option can be specified multiple times (default: bind to all interfaces) 68 | +# Bind to given address to listen for JSON-RPC connections. This option is ignored 69 | +# unless `-rpcallowip` is also passed. Port is optional and overrides `-rpcport`. 70 | +# Use [host]:port notation for IPv6. This option can be specified multiple 71 | +# times (default: 127.0.0.1 and ::1 i.e., localhost, or if `-rpcallowip` has 72 | +# been specified, 0.0.0.0 and :: i.e., all addresses)
Default is only ever localhost now.
@fanquake sorry missed the notifications. I think the best would be to generate the doc from the manpage as previously stated. I will make a PR if I have sometime. It would be great if someone could share previous work done on this task so I can pick it up
<!--5d09a71f8925f3f132321140b44b946d-->The last travis run for this pull request was 270 days ago and is thus outdated. To trigger a fresh travis build, this pull request should be closed and re-opened.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.