deep-stack/stack-orchestrator
3
0
Fork 0
forked from cerc-io/stack-orchestrator
Code Pull Requests Activity
333797b0c3
stack-orchestrator/app/data/stacks/fixturenet-lotus/README.md
prathamesh0 333797b0c3
Lotus stack usability improvements (#489) 
* move health check inside startup script

* remove pre-built genesis

* move health check inside startup script

* remove pre-built genesis

* Use hardcoded paths for Lotus node data directories

* Persist proof parameters

* Write out miner node's multiaddr with docker network IP

* Enable Lotus ETH RPC API and bind to all available interfaces

* Fund a known account

---------

Co-authored-by: iskay <ikay@lakeheadu.ca>
Co-authored-by: Ian Kay <ian@knowable.vc>
2023-08-09 17:24:47 +05:30

1012 B
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 logs lotus-miner
$ laconic-so --stack fixturenet-lotus deploy logs lotus-node-1
$ laconic-so --stack fixturenet-lotus deploy logs lotus-node-2

or by checking the chain status on each node:

$ laconic-so --stack fixturenet-lotus deploy exec lotus-miner "lotus status"
$ laconic-so --stack fixturenet-lotus deploy exec lotus-node-1 "lotus status"
$ laconic-so --stack fixturenet-lotus deploy exec lotus-node-2 "lotus status"