From e4ab1133fc4e19c8b83a72e6cab5a9b36ef50a09 Mon Sep 17 00:00:00 2001 From: prathamesh0 Date: Mon, 14 Aug 2023 12:20:20 +0530 Subject: [PATCH] Add clean up steps to instructions --- app/data/stacks/azimuth/README.md | 2 +- app/data/stacks/fixturenet-lotus/README.md | 19 +++++++++++++++++++ app/data/stacks/mobymask-v2/README.md | 2 +- app/data/stacks/sushiswap/README.md | 4 +++- 4 files changed, 24 insertions(+), 3 deletions(-) diff --git a/app/data/stacks/azimuth/README.md b/app/data/stacks/azimuth/README.md index c4e1671f..67f42b75 100644 --- a/app/data/stacks/azimuth/README.md +++ b/app/data/stacks/azimuth/README.md @@ -55,7 +55,7 @@ This should create the required docker images in the local image registry. ## Clean up -Stop all the services running in background run: +Stop all the services running in background: ```bash laconic-so --stack azimuth deploy-system down diff --git a/app/data/stacks/fixturenet-lotus/README.md b/app/data/stacks/fixturenet-lotus/README.md index 2e87e1b9..7d238347 100644 --- a/app/data/stacks/fixturenet-lotus/README.md +++ b/app/data/stacks/fixturenet-lotus/README.md @@ -14,6 +14,9 @@ $ laconic-so --stack fixturenet-lotus build-containers ``` $ laconic-so --stack fixturenet-lotus deploy --cluster lotus up ``` + +Note: When running for the first time (or after clean up), the services will take some time to start properly as the Lotus nodes download the proof params (which are persisted to volumes) + Correct operation should be verified by checking the container logs with: ``` $ laconic-so --stack fixturenet-lotus deploy --cluster lotus logs lotus-miner @@ -26,3 +29,19 @@ $ laconic-so --stack fixturenet-lotus deploy --cluster lotus exec lotus-miner "l $ laconic-so --stack fixturenet-lotus deploy --cluster lotus exec lotus-node-1 "lotus status" $ laconic-so --stack fixturenet-lotus deploy --cluster lotus exec lotus-node-2 "lotus status" ``` + +## 4. Clean up + +Stop all the services running in background: +``` +$ laconic-so --stack fixturenet-lotus deploy --cluster lotus down +``` + +Clear volumes created by this stack: +``` +# List all relevant volumes +$ docker volume ls -q --filter "name=lotus" + +# Remove all the listed volumes +$ docker volume rm $(docker volume ls -q --filter "name=lotus") +``` diff --git a/app/data/stacks/mobymask-v2/README.md b/app/data/stacks/mobymask-v2/README.md index dfbabd09..f4fc12e4 100644 --- a/app/data/stacks/mobymask-v2/README.md +++ b/app/data/stacks/mobymask-v2/README.md @@ -93,7 +93,7 @@ Follow the [demo](./demo.md) to try out the MobyMask app with L2 chain ## Clean up -Stop all the services running in background run: +Stop all the services running in background: ```bash laconic-so --stack mobymask-v2 deploy --cluster mobymask_v2 down 30 diff --git a/app/data/stacks/sushiswap/README.md b/app/data/stacks/sushiswap/README.md index 50450613..9d117f03 100644 --- a/app/data/stacks/sushiswap/README.md +++ b/app/data/stacks/sushiswap/README.md @@ -22,13 +22,15 @@ Deploy the stack: laconic-so --stack sushiswap deploy --cluster sushiswap up ``` +Note: When running for the first time (or after clean up), the services will take some time to start as Lotus nodes in the fixturenet download the proof params + ## Tests Follow [smoke-tests.md](./smoke-tests.md) to run smoke tests ## Clean up -Stop all the services running in background run: +Stop all the services running in background: ```bash laconic-so --stack sushiswap deploy --cluster sushiswap down