@@ -16,18 +16,18 @@ Quick start:
1616
1717``` bash
1818# L1 environment with mev-boost relay
19- builder-playground cook l1
19+ builder-playground start l1
2020
2121# L2 OpStack with external builder support
22- builder-playground cook opstack --external-builder http://localhost:4444
22+ builder-playground start opstack --external-builder http://localhost:4444
2323```
2424
2525## Getting started
2626
27- Clone the repository and use the ` cook ` command to deploy a specific recipe:
27+ Clone the repository and use the ` start ` command to deploy a specific recipe:
2828
2929``` bash
30- $ builder-playground cook < recipe>
30+ $ builder-playground start < recipe>
3131```
3232
3333Currently available recipes:
@@ -41,7 +41,7 @@ Deploys a complete L1 environment with:
4141- An in-memory [ mev-boost-relay] ( https://github.com/flashbots/mev-boost-relay ) .
4242
4343``` bash
44- $ builder-playground cook l1 [flags]
44+ $ builder-playground start l1 [flags]
4545```
4646
4747Flags:
@@ -61,7 +61,7 @@ Deploys an L2 environment with:
6161- A complete sequencer with op-node, op-geth and op-batcher
6262
6363``` bash
64- $ builder-playground cook opstack [flags]
64+ $ builder-playground start opstack [flags]
6565```
6666
6767Flags:
@@ -74,15 +74,15 @@ Flags:
7474Here's a complete example showing how to run the L1 recipe with the latest fork enabled and custom output directory:
7575
7676``` bash
77- $ builder-playground cook l1 --latest-fork --output ~ /my-builder-testnet --genesis-delay 15 --log-level debug
77+ $ builder-playground start l1 --latest-fork --output ~ /my-builder-testnet --genesis-delay 15 --log-level debug
7878```
7979
8080### Generate transaction flow with contender
8181
8282builder-playground can generate transaction flow to its nodes with [ contender] ( https://github.com/flashbots/contender ) . Just pass the ` --contender ` flag to send spam transactions that fill each block:
8383
8484``` bash
85- go run main.go cook l1 --contender
85+ go run main.go start l1 --contender
8686```
8787
8888The default contender flags are as follows:
@@ -95,7 +95,7 @@ To add or modify contender flags, use `--contender.arg`:
9595
9696``` bash
9797# run the builtin erc20 scenario instead of the default "fill block" scenario, at 100 TPS
98- go run main.go cook l1 --contender \
98+ go run main.go start l1 --contender \
9999 --contender.arg " --tps 100" \
100100 --contender.arg " erc20"
101101```
@@ -137,18 +137,30 @@ $ builder-playground inspect <service> <port>
137137Example:
138138
139139``` bash
140- $ builder-playground cook opstack
140+ $ builder-playground start opstack
141141$ builder-playground inspect op-geth authrpc
142142```
143143
144144This command starts a ` tcpflow ` container in the same network interface as the service and captures the traffic to the specified port.
145145
146146## Clean
147147
148- Removes a recipe running in the background
148+ Remove local playground sessions:
149149
150150``` bash
151- $ builder-playground clean [--output ./output]
151+ $ builder-playground stop all
152+ ```
153+
154+ You can also stop specific session:
155+
156+ ``` bash
157+ $ builder-playground list
158+ honest-opossum
159+ major-hornet
160+ sacred-giraffe
161+ $ builder-playground stop honest-opossum sacred-giraffe
162+ Cleaning session: honest-opossum
163+ Cleaning session: sacred-giraffe
152164```
153165
154166## Telemetry
@@ -167,8 +179,8 @@ By default, Prometheus scrapes the `/metrics` path, but services can override th
167179Enable Prometheus for any recipe:
168180
169181``` bash
170- $ builder-playground cook l1 --with-prometheus
171- $ builder-playground cook opstack --with-prometheus
182+ $ builder-playground start l1 --with-prometheus
183+ $ builder-playground start opstack --with-prometheus
172184```
173185
174186## Internals
0 commit comments