Dmitry
Dmitry
So, what are the requirements for the tool, and what are the exact problems we need to solve? My understanding so far about the problems: - `docker-compose.yml` in the repository...
The tool will generate a directory with `docker-compose.yml` and configurations for peers. This directory may also contain a cloned repo, depending on the arguments. - `source` - the main parameter....
> TBH it doesn’t have to be CLI. I would prefer a CLI tool, but that’s only because it’d be easier for **us** to maintain. @appetrosyan, I think it would...
After understanding more details of the task, I came to the conclusion that making `kagami swarm` a channel-agnostic tool (i.e. it can work with both `dev`, `stable` and `lts` channels)...
There are bugs and other tasks as separated issues, but this issue might be closed, I think. _upd:_ so we can close it only after verification, I see..
After some research and discussions, I came up with the following thoughts. ### Decision to abandon Directory Mode Currently, `kagami swarm` has two modes: Directory and File. Developing Directory Mode...
Mentally it is related to #169
If this issue is closed as not planned and we decide not to remove `pending_transactions` endpoint, we should not forget to document it in the Torii reference.
Yes, I would say that `configs/{client|peer}.template.toml` is an exhaustive coverage to see if there are user-facing changes in the config. However, these files aren't covered yet with tests to ensure...
I guess it will automatically close #2430