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
Copy file name to clipboardExpand all lines: resources/plugins/simln/README.md
+3-14Lines changed: 3 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,24 +91,13 @@ nodes:
91
91
92
92
plugins:
93
93
postDeploy:
94
-
# Take note: the path to the plugin file is relative to the `network.yaml` file. The location of your `plugin.py` file and `network.yaml` file may differ than what is shown below.
When using `warnet deploy <network folder>`, Warnet will look for a `network.yaml` in the network folder, and it will deploy the nodes listed in the `nodes` section of the file. We can choose to execute our plugin functions before Warnet deploys the nodes by including those functions in the `preDeploy` section of the `network.yaml` file. We can also choose to run plugin commands after Warnet deploys the nodes by including the function in the `postDeploy` section.
102
-
103
-
````yaml
104
-
plugins:
105
-
preDeploy:
106
-
- path/to/plugin.py setup_function
107
-
postDeploy:
108
-
- path/to/plugin.py run
109
-
- path/to/other/plugin.py run
110
-
````
111
-
112
101
113
102
## Generating your own SimLn image
114
103
The SimLN plugin fetches a SimLN docker image from dockerhub. You can generate your own docker image if you choose:
0 commit comments