Skip to content

Commit ecee15e

Browse files
committed
add quickrun doc
1 parent a3a9226 commit ecee15e

File tree

2 files changed

+45
-0
lines changed

2 files changed

+45
-0
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ Monitor and analyze the emergent behaviors of Bitcoin networks.
1616
## Documentation
1717

1818
- [Installation](https://github.com/bitcoin-dev-project/warnet/blob/main/docs/install.md)
19+
- [Quick Run](https://github.com/bitcoin-dev-project/warnet/blob/main/docs/quickrun.md)
1920
- [Running Warnet](https://github.com/bitcoin-dev-project/warnet/blob/main/docs/running.md)
2021
- [Network Topology](https://github.com/bitcoin-dev-project/warnet/blob/main/docs/graph.md)
2122
- [CLI Commands](https://github.com/bitcoin-dev-project/warnet/blob/main/docs/warcli.md)

docs/quickrun.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Quick run
2+
3+
Warnet runs a server which can be used to manage multiple networks. On docker
4+
this runs locally, but on Kubernetes this runs as a `statefulSet` in the
5+
cluster.
6+
7+
If the `$XDG_STATE_HOME` environment variable is set, the server will log to
8+
a file `$XDG_STATE_HOME/warnet/warnet.log`, otherwise it will use `$HOME/.warnet/warnet.log`.
9+
10+
## Quick start via pip
11+
12+
You can install warnet via `pip` into your virtual environment with
13+
14+
```bash
15+
python3 -m venv .venv
16+
source .venv/bin/activate
17+
pip install warnet
18+
```
19+
20+
Following installation `warcli` commands will operate natively on the Kubernetes cluster currently configured with `kubectl`.
21+
22+
Starting the Warnet server is as easy as:
23+
24+
```bash
25+
# (optional) if using a local minikube cluster check that we have all required programs installed
26+
warcli setup
27+
28+
# (optional) if using a local minikube cluster, set it up
29+
warcli cluster minikube-setup
30+
31+
warcli cluster deploy
32+
```
33+
34+
This also automatically configures port forwarding to the Server in the cluster.
35+
36+
To tear down the cluster:
37+
38+
```bash
39+
warcli cluster teardown
40+
41+
# (optional) if using a local minikube cluster, remove the image
42+
warcli cluster minikube-clean
43+
44+

0 commit comments

Comments
 (0)