rename warcli cmd to warnet

Author: willcl-ark

docs/connecting-local-nodes.md

@@ -7,8 +7,8 @@
 ### Run Warnet network
 
 ```shell
-warcli cluster deploy
-warcli network start
+warnet cluster deploy
+warnet network start
 ```
 
 ### Install Telepresence
@@ -71,9 +71,9 @@ telepresence intercept local-bitcoind --port 18444 -- bitcoind --regtest --datad
 ### Connect to local bitcoind from cluster
 
 ```shell
-warcli bitcoin rpc 0 addnode "local-bitcoind:18444" "onetry"
+warnet bitcoin rpc 0 addnode "local-bitcoind:18444" "onetry"
 # Check that the local node was added
-warcli bitcoin rpc 0 getpeerinfo
+warnet bitcoin rpc 0 getpeerinfo
 ```
 
 ### Disconnect and remove Telepresence
@@ -85,4 +85,4 @@ telepresence quit -s
 telepresent helm uninstall
 # Remove Telepresence from your computer
 sudo rm /usr/local/bin/telepresence
-```
+```

docs/lightning.md

@@ -42,22 +42,22 @@ data directory: [ln.graphml](../test/data/ln.graphml)
 
 ## Running the Lightning network
 
-When warnet is started with `warcli network start` the bitcoin containers will
+When warnet is started with `warnet network start` the bitcoin containers will
 be started first followed by the lightning node containers. It may require a few
 automatic restarts before the lightning nodes start up and connect to their
-corresponding bitcoin nodes. Use `warcli network status` to monitor container status
+corresponding bitcoin nodes. Use `warnet network status` to monitor container status
 and wait for all containers to be `running`.
 
 To create the lightning channels specified in the graph file, run the included
 scenario:
 
-`warcli scenarios run ln_init`
+`warnet scenarios run ln_init`
 
 This [scenario](../src/scenarios/ln_init.py) will generate blocks, fund the wallets
 in the bitcoin nodes, and open the channels from the graph. Each of these steps
 requires some waiting as transactions are confirmed in the warnet blockchain
 and lightning nodes gossip their channel announcements to each other.
-Use `warcli scenarios active` to monitor the status of the scenario. When it is
+Use `warnet scenarios active` to monitor the status of the scenario. When it is
 complete the subprocess will exit and it will indicate `Active: False`. At that
 point, the lightning network is ready for activity.
 
@@ -66,15 +66,15 @@ point, the lightning network is ready for activity.
 Warnet can export data required to run [sim-ln](https://github.com/bitcoin-dev-project/sim-ln)
 with a warnet network.
 
-With a network running, execute: `warcli network export` with optional argument
+With a network running, execute: `warnet network export` with optional argument
 `--network=<network name>` (default is "warnet"). This will copy all lightning
 node credentials like SSL certificates and macaroons into a local directory as
 well as generate a JSON file required by sim-ln.
 
 Example (see sim-ln docs for exact API):
 
 ```
-$ warcli network export
+$ warnet network export
 /Users/bitcoin-dev-project/.warnet/warnet/warnet/simln
 
 $ ls /Users/bitcoin-dev-project/.warnet/warnet/warnet/simln

docs/logging_monitoring.md

@@ -14,7 +14,7 @@ Examples of information provided:
 - what scenarios are running
 - warnet RPC requests
 
-Commands: `warcli network logs` or `warcli network logs --follow`.
+Commands: `warnet network logs` or `warnet network logs --follow`.
 
 See more details in [warcli](/docs/warcli.md#warcli-network-logs)
 
@@ -25,7 +25,7 @@ These are tank level or pod level log output from a Bitcoin Core node, useful fo
 Example:
 
 ```sh
-$ warcli bitcoin debug-log 0
+$ warnet bitcoin debug-log 0
 
 
 2023-10-11T17:54:39.616974Z Bitcoin Core version v25.0.0 (release build)
@@ -38,12 +38,12 @@ For logs of lightning nodes, kubectl is required.
 
 ### Aggregated logs from all nodes
 
-Aggregated logs can be searched using `warcli bitcoin grep-logs` with regex patterns.
+Aggregated logs can be searched using `warnet bitcoin grep-logs` with regex patterns.
 
 Example:
 
 ```sh
-$ warcli bitcoin grep-logs 94cacabc09b024b56dcbed9ccad15c90340c596e883159bcb5f1d2152997322d
+$ warnet bitcoin grep-logs 94cacabc09b024b56dcbed9ccad15c90340c596e883159bcb5f1d2152997322d
 
 warnet_test_uhynisdj_tank_000001: 2023-10-11T17:44:48.716582Z [miner] AddToWallet 94cacabc09b024b56dcbed9ccad15c90340c596e883159bcb5f1d2152997322d  newupdate
 warnet_test_uhynisdj_tank_000001: 2023-10-11T17:44:48.717787Z [miner] Submitting wtx 94cacabc09b024b56dcbed9ccad15c90340c596e883159bcb5f1d2152997322d to mempool for relay
@@ -77,7 +77,7 @@ It might take a couple minutes to get the pod running. If you see `error: unable
 The Grafana dashboard (and API) will be accessible without requiring authentication
 at `http://localhost:3000`.
 
-The `install_logging` script will need to be installed before starting the network in order to collect the information for monitoring and metrics. Restart the network with `warcli network down && warcli network up` if necessary.
+The `install_logging` script will need to be installed before starting the network in order to collect the information for monitoring and metrics. Restart the network with `warnet network down && warnet network up` if necessary.
 
 ### Prometheus
 

docs/quickrun.md

@@ -29,36 +29,36 @@ pip install -e .
 ## Running
 
 > [!TIP]
-> When developing locally add the `--dev` flag to `warcli cluster deploy` to enable dev mode with hot-reloading server.
+> When developing locally add the `--dev` flag to `warnet cluster deploy` to enable dev mode with hot-reloading server.
 
 ### Using minikube
 
 To run a local cluster using minikube:
 
 ```bash
-warcli cluster setup-minikube
+warnet cluster setup-minikube
 
-warcli cluster deploy
+warnet cluster deploy
 ```
 
 ### Other cluster types
 
-If not using minikube (e.g. using Docker Desktop or a managed cluster), `warcli` commands will operate natively on the current Kubernetes context, so you can simply run:
+If not using minikube (e.g. using Docker Desktop or a managed cluster), `warnet` commands will operate natively on the current Kubernetes context, so you can simply run:
 
 ```bash
-warcli cluster deploy
+warnet cluster deploy
 ```
 
 ...to deploy warnet to your cluster.
 
-`warcli cluster deploy` also automatically configures port forwarding to the Server in the cluster.
+`warnet cluster deploy` also automatically configures port forwarding to the Server in the cluster.
 
 ## Stopping
 
 To tear down the cluster:
 
 ```bash
-warcli cluster teardown
+warnet cluster teardown
 ```
 
 ## Log location

docs/running.md

@@ -8,31 +8,31 @@ See more details in [warcli](/docs/warcli.md), examples:
 To start the server run:
 
 ```bash
-warcli cluster deploy
+warnet cluster deploy
 ```
 
 Start a network from a graph file:
 
 ```bash
-warcli network start resources/graphs/default.graphml
+warnet network start resources/graphs/default.graphml
 ```
 
 Make sure all tanks are running with:
 
 ```bash
-warcli network status
+warnet network status
 ```
 
 Check if the edges of the graph (bitcoin p2p connections) are complete:
 
 ```bash
-warcli network connected
+warnet network connected
 ```
 
 _Optional_ Check out the logs with:
 
 ```bash
-warcli network logs -f
+warnet network logs -f
 ```
 
 If that looks all good, give [scenarios](/docs/scenarios.md) a try.

docs/scenarios.md

@@ -10,37 +10,37 @@ See [`src/warnet/scenarios`](../src/warnet/scenarios) for examples of how these
 To see available scenarios (loaded from the default directory):
 
 ```bash
-warcli scenarios available
+warnet scenarios available
 ```
 
-Once a scenario is selected it can be run with `warcli scenarios run [--network=warnet] <scenario_name> [scenario_params]`.
+Once a scenario is selected it can be run with `warnet scenarios run [--network=warnet] <scenario_name> [scenario_params]`.
 
 The [`miner_std`](../src/warnet/scenarios/miner_std.py) scenario is a good one to start with as it automates block generation:
 
 ```bash
 # Have all nodes generate a block 5 seconds apart in a round-robin
-warcli scenarios run miner_std --allnodes --interval=5
+warnet scenarios run miner_std --allnodes --interval=5
 ```
 
 This will run the scenario in a background thread on the server until it exits or is stopped by the user.
 
 Active scenarios can be listed and terminated by PID:
 
 ```bash
-$ warcli scenarios available
+$ warnet scenarios available
 miner_std      Generate blocks over time. Options: [--allnodes | --interval=<number> | --mature]
 sens_relay     Send a transaction using sensitive relay
 tx_flood       Generate 100 blocks with 100 TXs each
 
-$ warcli scenarios run tx_flood
+$ warnet scenarios run tx_flood
 Running scenario tx_flood with PID 14683 in the background...
 
-$ warcli scenarios active
+$ warnet scenarios active
       ┃ Active ┃ Cmd       ┃ Network ┃ Pid   ┃ Return_code ┃
       ┡━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━╇━━━━━━━━━━━━━┩
       │ True   │ tx_flood  │ warnet  │ 14683 │ None        ┃
 
-$ warcli scenarios stop 14683
+$ warnet scenarios stop 14683
 Stopped scenario with PID 14683.
 ```
 
@@ -50,5 +50,5 @@ You can write your own scenario file locally and upload it to the server with
 the [run-file](/docs/warcli.md#warcli-scenarios-run-file) command (example):
 
 ```bash
-warcli scenarios run-file /home/me/bitcoin_attack.py
+warnet scenarios run-file /home/me/bitcoin_attack.py
 ```