ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-23 06:42:33 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Docs: Removed remaining references to webAddress in the node config (#3467)

Browse Source
This commit is contained in:
Shams Asari 2018-06-28 15:03:27 +01:00 committed by GitHub
parent 76c114502e
commit d5b5825c09
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
config/dev/generalnodea.conf
View File

@ -3,4 +3,3 @@ keyStorePassword : "cordacadevpass"
trustStorePassword : "trustpass" trustStorePassword : "trustpass"
p2pAddress : "localhost:10002" p2pAddress : "localhost:10002"
rpcAddress : "localhost:10003" rpcAddress : "localhost:10003"
webAddress : "localhost:10004"

1
config/dev/generalnodeb.conf
View File

@ -3,4 +3,3 @@ keyStorePassword : "cordacadevpass"
trustStorePassword : "trustpass" trustStorePassword : "trustpass"
p2pAddress : "localhost:10005" p2pAddress : "localhost:10005"
rpcAddress : "localhost:10006" rpcAddress : "localhost:10006"
webAddress : "localhost:10007"

1
config/dev/nameservernode.conf
View File

@ -2,7 +2,6 @@ myLegalName : "O=Notary Service,OU=corda,L=London,C=GB"
keyStorePassword : "cordacadevpass" keyStorePassword : "cordacadevpass"
trustStorePassword : "trustpass" trustStorePassword : "trustpass"
p2pAddress : "localhost:10000" p2pAddress : "localhost:10000"
webAddress : "localhost:10001"
notary : { notary : {
validating : true validating : true
} }

2
docs/source/deploying-a-node.rst
View File

@ -38,7 +38,6 @@ handling, and ensures the Corda service is run at boot.
basedir : "/opt/corda" basedir : "/opt/corda"
p2pAddress : "example.com:10002" p2pAddress : "example.com:10002"
rpcAddress : "example.com:10003" rpcAddress : "example.com:10003"
webAddress : "0.0.0.0:10004"
h2port : 11000 h2port : 11000
emailAddress : "you@example.com" emailAddress : "you@example.com"
myLegalName : "O=Bank of Breakfast Tea, L=London, C=GB" myLegalName : "O=Bank of Breakfast Tea, L=London, C=GB"
@ -203,7 +202,6 @@ at boot, and means the Corda service stays running with no users connected to th
basedir : "C:\\Corda" basedir : "C:\\Corda"
p2pAddress : "example.com:10002" p2pAddress : "example.com:10002"
rpcAddress : "example.com:10003" rpcAddress : "example.com:10003"
webAddress : "0.0.0.0:10004"
h2port : 11000 h2port : 11000
emailAddress: "you@example.com" emailAddress: "you@example.com"
myLegalName : "O=Bank of Breakfast Tea, L=London, C=GB" myLegalName : "O=Bank of Breakfast Tea, L=London, C=GB"

4
docs/source/setting-up-a-corda-network.rst
View File

@ -42,8 +42,6 @@ The most important fields regarding network configuration are:
is the hostname *that must be externally resolvable by other nodes in the network*. In the above configuration this is the is the hostname *that must be externally resolvable by other nodes in the network*. In the above configuration this is the
resolvable name of a machine in a VPN. resolvable name of a machine in a VPN.
* ``rpcAddress``: The address to which Artemis will bind for RPC calls. * ``rpcAddress``: The address to which Artemis will bind for RPC calls.
* ``webAddress``: The address the webserver should bind. Note that the port must be distinct from that of ``p2pAddress``
and ``rpcAddress`` if they are on the same machine.
* ``notary.serviceLegalName``: The name of the notary service, required to setup distributed notaries with the network-bootstrapper. * ``notary.serviceLegalName``: The name of the notary service, required to setup distributed notaries with the network-bootstrapper.
Starting the nodes Starting the nodes
@ -55,8 +53,6 @@ be found in :doc:`network-bootstrapper`.
Once that's done you may now start the nodes in any order. You should see a banner, some log lines and eventually Once that's done you may now start the nodes in any order. You should see a banner, some log lines and eventually
``Node started up and registered``, indicating that the node is fully started. ``Node started up and registered``, indicating that the node is fully started.
.. TODO: Add a better way of polling for startup. A programmatic way of determining whether a node is up is to check whether it's ``webAddress`` is bound.
In terms of process management there is no prescribed method. You may start the jars by hand or perhaps use systemd and friends. In terms of process management there is no prescribed method. You may start the jars by hand or perhaps use systemd and friends.
Logging Logging