ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-02-06 11:09:18 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fixes formatting. Fixes link. (#3693)

Browse Source
This commit is contained in:
Joel Dudley 2018-07-26 10:09:35 +01:00 committed by GitHub
parent cdddd84e6b
commit 4075e29120
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/source/blob-inspector.rst
View File

@ -2,11 +2,11 @@ Blob Inspector
============== ==============
There are many benefits to having a custom binary serialisation format (see :doc:`serialization` for details) but one There are many benefits to having a custom binary serialisation format (see :doc:`serialization` for details) but one
disadvantage is the inability to view the contents in a human-friendly manner. The blob inspector tool alleviates this issue disadvantage is the inability to view the contents in a human-friendly manner. The Corda Blob Inspector tool alleviates
by allowing the contents of a binary blob file (or URL end-point) to be output in either YAML or JSON. It uses this issue by allowing the contents of a binary blob file (or URL end-point) to be output in either YAML or JSON. It
``JacksonSupport`` to do this (see :doc:`json`). uses ``JacksonSupport`` to do this (see :doc:`json`).
The latest version of the tool can be downloaded from `here <https://corda.net/resources>`_. The tool can be downloaded from `here <https://corda.net/resources>`_.
To run simply pass in the file or URL as the first parameter:: To run simply pass in the file or URL as the first parameter::
@ -51,8 +51,9 @@ Example
Here's what a node-info file from the node's data directory may look like: Here's what a node-info file from the node's data directory may look like:
**-\\-format=YAML** * YAML:
::
.. sourcecode:: none
net.corda.nodeapi.internal.SignedNodeInfo net.corda.nodeapi.internal.SignedNodeInfo
--- ---
@ -69,8 +70,9 @@ Here's what a node-info file from the node's data directory may look like:
- !!binary |- - !!binary |-
VFRy4frbgRDbCpK1Vo88PyUoj01vbRnMR3ROR2abTFk7yJ14901aeScX/CiEP+CDGiMRsdw01cXt\nhKSobAY7Dw== VFRy4frbgRDbCpK1Vo88PyUoj01vbRnMR3ROR2abTFk7yJ14901aeScX/CiEP+CDGiMRsdw01cXt\nhKSobAY7Dw==
**-\\-format=JSON** * JSON:
::
.. sourcecode:: none
net.corda.nodeapi.internal.SignedNodeInfo net.corda.nodeapi.internal.SignedNodeInfo
{ {

3
docs/source/network-bootstrapper.rst
View File

@ -24,8 +24,7 @@ You can find out more about network maps and network parameters from :doc:`netwo
Bootstrapping a test network Bootstrapping a test network
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The bootstrapper can be downloaded from https://downloads.corda.net/network-bootstrapper-VERSION.jar, where ``VERSION`` The Corda Network Bootstrapper can be downloaded from `here <https://corda.net/resources>`_.
is the Corda version.
Create a directory containing a node config file, ending in "_node.conf", for each node you want to create. Then run the Create a directory containing a node config file, ending in "_node.conf", for each node you want to create. Then run the
following command: following command: