At the last community call @matthew1001 raise the fact that the CLI arguments have become confusing and contradictory. Presence of contradictory flags doest not throw an error and the behaviour is confusing to users:
--remote-node-url and -n should not work together as one is pointing to a remote node and the other specifying what flavour (besu for example) to run a node locally in Docker.
--contract-address and --remote-node-deploy some confusing caused on how to deploy the multiparty contract
@nguyer made a great comment to highlight that this CLI was built to be able to quickly run Firefly locally for development and not intended for production. There are set of helm charts for that https://github.com/hyperledger/firefly-helm-charts
At the last community call @matthew1001 raise the fact that the CLI arguments have become confusing and contradictory. Presence of contradictory flags doest not throw an error and the behaviour is confusing to users:
--remote-node-urland-nshould not work together as one is pointing to a remote node and the other specifying what flavour (besu for example) to run a node locally in Docker.--contract-addressand--remote-node-deploysome confusing caused on how to deploy the multiparty contract@nguyer made a great comment to highlight that this CLI was built to be able to quickly run Firefly locally for development and not intended for production. There are set of helm charts for that https://github.com/hyperledger/firefly-helm-charts
@matthew1001 feel free to add more information!