feat(docker): add data persistence to docker-compose#834
feat(docker): add data persistence to docker-compose#834unwrap-nicolas wants to merge 1 commit intogetfloresta:masterfrom
Conversation
|
Should be marked as draft until 639 is merged |
|
Why does this need #639? I think you can just drop it and leave the persistence part |
4203acb to
0808d85
Compare
|
@Davidson-Souza actually, my goal with this PR is to get the monitoring stack running 100% smoothly with docker-compose. One issue I noticed was the lack of persistence. However, while fixing that, I realized that PR #639 doesn't fully accomplish its goal of "provisioning grafana dashboards via docker-compose" But your point makes sense. I've updated this PR's description and removed those specific fixes. I also added them as suggestions on PR #639. Thanks for the review! |
| command: >- | ||
| florestad --data-dir /data/.floresta | ||
| -n ${NETWORK:-bitcoin} | ||
| --rpc-address 0.0.0.0:8332 |
There was a problem hiding this comment.
Which port we are using depends on the network. Do you think it's possible to switch ports given the network?
Description and Notes
fixed #795
this PR addresses the lack of data persistence and network flexibility in the current
docker-compose.ymlsetup.currently, users running
docker compose upexperience:Changes
Data Persistence:
FLORESTA_DATAenvironment variable to reuse existing local blockchain data (useful for sharing data between native and Docker installations)Network Configuration:
NETWORKenvironment variable to easily switch between Bitcoin networks (bitcoin,signet,testnet,testnet4,regtest)--rpc-addressand--electrum-addressflags, avoiding port conflicts when changing networksDocumentation:
doc/docker.mdwith examples for running different networks and using local data directoriesHow to verify the changes you have done?
Start the stack:
docker compose up -dorNETWORK=signet FLORESTA_DATA=$HOME/.floresta docker compose up