mirror of https://github.com/nucypher/nucypher.git
RFCs to docs. Bug fix to CLI config.
parent
af5a938219
commit
b35fe78eaa
|
@ -33,6 +33,7 @@ The first step is to launch the first Ursula on the network by running:
|
|||
|
||||
.. code::
|
||||
|
||||
$ cd scripts/local_fleet
|
||||
$ python run_lonely_ursula.py
|
||||
|
||||
This will start an Ursula node:
|
||||
|
@ -42,7 +43,7 @@ This will start an Ursula node:
|
|||
|
||||
3. Run a Local Fleet of Ursulas
|
||||
|
||||
Next, launch subsequent Ursulas, informing them of the first Ursula:
|
||||
Next, launch subsequent Ursulas in another terminal, informing them of the first Ursula:
|
||||
|
||||
|
||||
.. code::
|
||||
|
|
|
@ -51,7 +51,7 @@ Here is the recommended procedure for setting up `nucypher` in this fashion:
|
|||
$(nucypher-venv)
|
||||
```
|
||||
|
||||
``` note:: Successful virtualenv activation is indicated by '(nucypher-venv)$' prepending your console's prompt
|
||||
``` note:: Successful virtualenv activation is indicated by '(nucypher-venv)$' prepended to your console's prompt
|
||||
```
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue