You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [For Developers Working on Hedera Service Repo](#for-developers-working-on-hedera-service-repo)
27
+
* [For Developers Working on Platform core](#for-developers-working-on-platform-core)
28
+
* [Using IntelliJ remote debug with Solo](#using-intellij-remote-debug-with-solo)
29
+
* [Retrieving Logs](#retrieving-logs)
30
+
* [Save and reuse network state files](#save-and-reuse-network-state-files)
26
31
* [Support](#support)
27
32
* [Contributing](#contributing)
28
33
* [Code of Conduct](#code-of-conduct)
@@ -53,17 +58,48 @@ nvm use lts/hydrogen
53
58
54
59
* Run `npm install -g @hashgraph/solo`
55
60
56
-
## Setup Kubernetes cluster
61
+
## Use the Task tool to launch Solo
57
62
58
-
### Remote cluster
63
+
First, install the cluster tool `kind` with this [link](https://kind.sigs.k8s.io/docs/user/quick-start#installation)
64
+
65
+
Then, install the task tool `task` with this [link](https://taskfile.dev/#/installation)
66
+
67
+
Then, use the following steps to install dependencies and build solo project.
68
+
69
+
```bash
70
+
npm ci
71
+
npm run build
72
+
```
73
+
Then, user can use one of the following three commands to quickly deploy a standalone solo network.
74
+
75
+
```bash
76
+
# Option 1) deploy solo network with two nodes
77
+
task default
78
+
79
+
# Option 2) deploy solo network with two nodes, and mirror node
80
+
task default-with-mirror
81
+
82
+
# Option 3) deploy solo network with two nodes, mirror node, and JSON RPC relay
83
+
task default-with-relay
84
+
```
85
+
To tear down the solo network
86
+
```bash
87
+
task clean
88
+
```
89
+
90
+
## Advanced User Guide
91
+
For those who would like to have more control or need some customized setups, here are some step by step instructions of how to setup and deploy a solo network.
92
+
### Setup Kubernetes cluster
93
+
94
+
#### Remote cluster
59
95
60
96
* You may use remote kubernetes cluster. In this case, ensure kubernetes context is set up correctly.
61
97
62
98
```
63
99
kubectl config use-context <context-name>
64
100
```
65
101
66
-
### Local cluster
102
+
#### Local cluster
67
103
68
104
* You may use [kind](https://kind.sigs.k8s.io/) or [microk8s](https://microk8s.io/) to create a cluster. In this case,
69
105
ensure your Docker engine has enough resources (e.g. Memory >=8Gb, CPU: >=4). Below we show how you can use `kind` to create a cluster
@@ -116,9 +152,8 @@ You may now view pods in your cluster using `k9s -A` as below:
You can find log for running solo command under the directory `~/.solo/logs/`
348
383
The file `solo.log` contains the logs for the solo command.
349
384
The file `hashgraph-sdk.log` contains the logs from Solo client when sending transactions to network nodes.
350
385
351
-
## Using IntelliJ remote debug with Solo
386
+
### Using IntelliJ remote debug with Solo
352
387
353
388
NOTE: the hedera-services path referenced '../hedera-services/hedera-node/data' may need to be updated based on what directory you are currently in. This also assumes that you have done an assemble/build and the directory contents are up-to-date.
0 commit comments