Lotus stack usability improvements #489

2023-08-07T05:24:51Z

prathamesh0 commented

2023-08-07 05:24:51 +00:00

(Migrated from github.com)

Part of https://github.com/cerc-io/stack-orchestrator/issues/481
Based on top of fixes / changes from https://github.com/cerc-io/stack-orchestrator/pull/483

Use hardcoded paths for Lotus node data directories as was being done previously
- Using $HOME as base was resolving to user's local home directory which is not accessible inside docker
Persist proof parameters (~2GB in size) to volumes so that they don't have to be fetched every time user brings up the stack
- Make use of the --cluster flag so that required volumes can be reused between re-runs
Write out miner node's multiaddr with docker network's IP
- Earlier, the multiaddr with loopback address was being written out, which wasn't accessible from the client nodes
Enable the ETH RPC API and use 0.0.0.0 in the listen address to make it accessible from outside docker
Fund a known account in the miner setup so that it can be used in testing

Part of https://github.com/cerc-io/stack-orchestrator/issues/481 Based on top of fixes / changes from https://github.com/cerc-io/stack-orchestrator/pull/483 - Use hardcoded paths for Lotus node data directories as was being done previously - Using `$HOME` as base was resolving to user's local home directory which is not accessible inside docker - Persist proof parameters (~2GB in size) to volumes so that they don't have to be fetched every time user brings up the stack - Make use of the `--cluster` flag so that required volumes can be reused between re-runs - Write out miner node's multiaddr with docker network's IP - Earlier, the multiaddr with loopback address was being written out, which wasn't accessible from the client nodes - Enable the ETH RPC API and use `0.0.0.0` in the listen address to make it accessible from outside docker - Fund a known account in the miner setup so that it can be used in testing

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#489