Skip to content

Commit b9ac871

Browse files
committed
[FAB-9913] Remove last vestiges of "-m" from byfn.sh
Given that the "-m" option is deprecated WRT byfn.sh, delete the final occurrences of that in docs/source/. Change-Id: I7e04b2d82feac9fe1ac1b752aad02588b800251b Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
1 parent 448d54c commit b9ac871

File tree

3 files changed

+11
-11
lines changed

3 files changed

+11
-11
lines changed

docs/source/channel_update_tutorial.rst

+6-6
Original file line numberDiff line numberDiff line change
@@ -44,19 +44,19 @@ previous environments:
4444

4545
.. code:: bash
4646
47-
./byfn.sh -m down
47+
./byfn.sh down
4848
4949
Now generate the default BYFN artifacts:
5050

5151
.. code:: bash
5252
53-
./byfn.sh -m generate
53+
./byfn.sh generate
5454
5555
And launch the network making use of the scripted execution within the CLI container:
5656

5757
.. code:: bash
5858
59-
./byfn.sh -m up
59+
./byfn.sh up
6060
6161
Now that you have a clean version of BYFN running on your machine, you have two
6262
different paths you can pursue. First, we offer a fully commented script that will
@@ -87,7 +87,7 @@ If everything goes well, you'll get this message:
8787
========= All GOOD, EYFN test execution completed ===========
8888
8989
``eyfn.sh`` can be used with the same Node.js chaincode and database options
90-
as ``byfn.sh`` by issuing the following (instead of ``./byfn.sh -m -up``):
90+
as ``byfn.sh`` by issuing the following (instead of ``./byfn.sh up``):
9191

9292
.. code:: bash
9393
@@ -156,13 +156,13 @@ When the network is down, bring it back up again.
156156

157157
.. code:: bash
158158
159-
./byfn.sh -m generate
159+
./byfn.sh generate
160160
161161
Then:
162162

163163
.. code:: bash
164164
165-
./byfn.sh -m up
165+
./byfn.sh up
166166
167167
This will bring your network back to the same state it was in before you executed
168168
the ``eyfn.sh`` script.

docs/source/upgrading_your_network_tutorial.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ and remove any previously generated artifacts. Run the following command:
7272

7373
.. code:: bash
7474
75-
./byfn.sh -m down
75+
./byfn.sh down
7676
7777
Generate the Crypto and Bring Up the Network
7878
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -85,9 +85,9 @@ With a clean environment, launch our v1.0.6 BYFN network using these four comman
8585
8686
git checkout v1.0.6
8787
88-
./byfn.sh -m generate
88+
./byfn.sh generate
8989
90-
./byfn.sh -m up -t 3000 -i 1.0.6
90+
./byfn.sh up -t 3000 -i 1.0.6
9191
9292
.. note:: If you have locally built v1.0.6 images, then they will be used by the example.
9393
If you get errors, consider cleaning up v1.0.6 images and running the example
@@ -141,7 +141,7 @@ If the upgrade is successful, you should see the following:
141141
142142
===================== All GOOD, End-2-End UPGRADE Scenario execution completed =====================
143143
144-
if you want to upgrade the network manually, simply run ``./byfn.sh -m down`` again
144+
if you want to upgrade the network manually, simply run ``./byfn.sh down`` again
145145
and perform the steps up to -- but not including -- ``./byfn.sh upgrade -i 1.1.x``.
146146
Then proceed to the next section.
147147

docs/source/write_first_app.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ down any existing networks you have, which you can do by issuing the following:
4343

4444
.. code:: bash
4545
46-
./byfn.sh -m down
46+
./byfn.sh down
4747
4848
If you don't have a development environment and the accompanying artifacts for
4949
the network and applications, visit the :doc:`prereqs` page and ensure you have

0 commit comments

Comments
 (0)