* Add a sushiswap stack with contract deployments

* Add watcher services

* Add a service for the info app

* Add instructions to run smoke tests

* Use sushi-info-watcher in demo mode

* Turn off block prefetching

* Fix sushiswap demo instructions

* Use release version and add healthcheck in Lotus stack

* Wait for Lotus node to start before sushiswap watchers

---------

Co-authored-by: Nabarun <nabarun@deepstacksoft.com>

2023-08-10 13:57:07 +05:30

1.1 KiB

Raw Blame History

Lotus Fixturenet

Instructions for deploying a local Lotus (Filecoin) chain for development and testing purposes using laconic-stack-orchestrator.

1. Clone required repositories

$ laconic-so --stack fixturenet-lotus setup-repositories

2. Build the stack's packages and containers

$ laconic-so --stack fixturenet-lotus build-containers

3. Deploy the stack

$ laconic-so --stack fixturenet-lotus deploy --cluster lotus up

Correct operation should be verified by checking the container logs with:

$ laconic-so --stack fixturenet-lotus deploy --cluster lotus logs lotus-miner
$ laconic-so --stack fixturenet-lotus deploy --cluster lotus logs lotus-node-1
$ laconic-so --stack fixturenet-lotus deploy --cluster lotus logs lotus-node-2

or by checking the chain status on each node:

$ laconic-so --stack fixturenet-lotus deploy --cluster lotus exec lotus-miner "lotus status"
$ 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"

1.1 KiB Raw Blame History

Lotus Fixturenet

1. Clone required repositories

2. Build the stack's packages and containers

3. Deploy the stack

1.1 KiB

Raw Blame History