mirror of
https://github.com/corda/corda.git
synced 2024-12-20 13:33:12 +00:00
Fix text errors
Signed-off-by: Ed Prosser <edward.prosser@r3.com>
This commit is contained in:
parent
4e6edd012a
commit
91d3ab3556
@ -7,10 +7,7 @@ Handcrafting a node
|
|||||||
-------------------
|
-------------------
|
||||||
A node can be created manually by creating a folder that contains the following items:
|
A node can be created manually by creating a folder that contains the following items:
|
||||||
|
|
||||||
* The Corda Enterprise JAR
|
* The Corda JAR, downloaded from https://r3.bintray.com/corda/net/corda/corda/ (under /|corda_version|/corda-|corda_version|.jar)
|
||||||
|
|
||||||
* The binary ``corda-|corda_version|.jar`` provided to your organisation.
|
|
||||||
|
|
||||||
* A node configuration file entitled ``node.conf``, configured as per :doc:`corda-configuration-file`
|
* A node configuration file entitled ``node.conf``, configured as per :doc:`corda-configuration-file`
|
||||||
|
|
||||||
* A folder entitled ``cordapps`` containing any CorDapp JARs you want the node to load
|
* A folder entitled ``cordapps`` containing any CorDapp JARs you want the node to load
|
||||||
@ -84,8 +81,6 @@ in the `Kotlin CorDapp Template <https://github.com/corda/cordapp-template-kotli
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
Ensure Corda Enterprise binaries are available on your machine as described in :ref:`Getting Set Up <resolve-corda-enterprise-binaries>`.
|
|
||||||
|
|
||||||
Running this task will create three nodes in the ``build/nodes`` folder:
|
Running this task will create three nodes in the ``build/nodes`` folder:
|
||||||
|
|
||||||
* A ``Notary`` node that:
|
* A ``Notary`` node that:
|
||||||
@ -237,9 +232,6 @@ Following the previous example ``PartyB`` node will have additional configuratio
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
Additional properties can be also specified directly by the ``extraConfig`` property which defines a map of keys and values. The example config above uses ``extraConfig`` to set value of the ``jvmArgs`` property.
|
|
||||||
See the extended example of :ref:`adding database configuration <testing_cordform_ref>`.
|
|
||||||
|
|
||||||
Cordform parameter `drivers` of the `node` entry lists paths of the files to be copied to the `./drivers` subdirectory of the node.
|
Cordform parameter `drivers` of the `node` entry lists paths of the files to be copied to the `./drivers` subdirectory of the node.
|
||||||
To copy the same file to all nodes `ext.drivers` can be defined in the top level and reused for each node via `drivers=ext.drivers``.
|
To copy the same file to all nodes `ext.drivers` can be defined in the top level and reused for each node via `drivers=ext.drivers``.
|
||||||
|
|
||||||
@ -278,7 +270,7 @@ To specify :doc:`design/data-model-upgrades/package-namespace-ownership` configu
|
|||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
Signing Cordapp JARs
|
Signing CorDapp JARs
|
||||||
^^^^^^^^^^^^^^^^^^^^
|
^^^^^^^^^^^^^^^^^^^^
|
||||||
The default behaviour of Cordform is to deploy CorDapp JARs "as built":
|
The default behaviour of Cordform is to deploy CorDapp JARs "as built":
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user