aiolabs/nix-bitcoin
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

docs/configuration: improve section Remote bitcoind

Browse source
This commit is contained in:
Erik Arvstedt 2022-08-22 14:57:40 +02:00
parent af115d746b
commit 3a65dc0dc9
No known key found for this signature in database
GPG key ID: 33312B944DD97846
1 changed files with 7 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/configuration.md
View file

@ -214,18 +214,15 @@ services.bitcoind = {
}; };
``` ```
If a `secure-node.nix` or `tor-enable.nix` preset is imported in your For each service that connects to bitcoind and has option
configuration or a `tor.enforce` option is explicitly enabled, you also need to `services.<service>.tor.enforce` enabled (either explicitly or by importing
allow remote connections for **every** service which needs to connect to the `secure-node.nix` or `enable-tor.nix`), you need to
remote bitcoind: allow the remote bitcoind connection:
```nix
``` systemd.services.<service>.serviceConfig.IPAddressAllow = [ ${services.bitcoind.rpc.address} ];
systemd.services.<service>.serviceConfig = {
IPAddressAllow = [ ${services.bitcoind.rpc.address} ];
};
``` ```
> Please note that configuration above applies only if the remote bitcoind **is > The above configuration is only required if the remote bitcoind **is
> not** accessed via Tor. > not** accessed via Tor.