feat: instantiate tanssi container chains #285
Conversation
Co-authored-by: Frank Bell <[email protected]>
Co-authored-by: Frank Bell <[email protected]>
* refactor: directories instead of folders * style: fmt * stable fmt
al3mart
changed the title
|
This is now ready for review @AlexD10S Instantiation should be sorted. Leaving everything related to deployment for a following PR where we can take care of sourcing, preparing the specs and other nits required to fit Tanssi use case. |
|
Great stuff, looking forward to trying it out. Suggest we hold off merging until the deployment PR is ready. Perhaps it could be a PR based on this one so it's easier to test when ready. |
…argo refactor: improve conatiner workspace instantiation
evilrobot-01
changed the title
| name = "collator-01" | ||
|
|
||
| [[parachains.collators]] | ||
| name = "collator-02" |
There was a problem hiding this comment.
Do we need to run this many collators in a dev environment? Think of a dev with limited resources on their machine. This might give a bad experience.
| name = "charlie" | ||
| validator = true | ||
|
|
||
| [[relaychain.nodes]] |
There was a problem hiding this comment.
Do we need to run this many collators in a dev environment? Think of a dev with limited resources on their machine. This might give a bad experience.
| @@ -0,0 +1,43 @@ | |||
| [workspace] | |||
There was a problem hiding this comment.
Not sure about this to be honest, its putting pressure on us to maintain and track the changes to their Cargo.toml if that is the purpose.
Can we not just use their version from the cloned/downloaded source code and amend that to avoid this file?
There was a problem hiding this comment.
Agreed, we can depend solely on the source manifest to craft these. It will require some tweaks in the logic. But nothing impossible.
This change allow users to instantiate Tanssi compatible container chain templates with
pop new parachain.