More control over docker-compose content
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- blockchain, docker, docker-compose
- Domain
- blockchain, devops, infrastructure
Research direction
The issue names the FF-CLI and Docker Compose as the relevant entry points, but no files or tests are identified. Start by reviewing how the CLI generates and overrides Compose content; done would mean a defined way to omit built-in blockchain and IPFS nodes, use external ones, and run the required setup steps.
Written by the indexing model from the issue text.
Description
I'm facing a situation where I'm already have a IPFS private network and a private permissioned blockchain.
My goal is to not allow FF to create its own blockchain node and use the one I have instead in native way (I mean in replacement of its own, not using connectors - I don't want an extra node in same machine )
Another thing is to use a customized IPFS node to connect in to my own network.
Some things I must do like empty the Bootsrap list of the IPFS config, add my own bootstrap, add my swarm file instead pass it from the compose (I may change it without to re run all the compose again - who knows?)
In the same way I need to make some adjusts in the Blockchain node to fit my needs.
In short, I must run some scripts before these components come up.
What I suggest is to allow to remove these pieces from the compose and run they "by hand". I don't know if I can do it using the override compose. By the way... why can't we just edit the compose instead using an override file? Is that possible to remove things from compose using the override file?
OR ....
Maybe you guys want to publish in some documents the step-by-step on how to build all the stack "by hand" ... from the docker pull to contract publishing ...all these things hidden by the FF-CLI so we may do more "granularity" ...
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
compress: block buffers get re-zeroed on every call, and the zeroing is immediately overwrittenOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/ch-go#1218 ·
Maintainers usually reply within 13 days
-
automation models
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
podman-container-tools/podman#30031 ·
Maintainers usually reply within 1 day