We need to define a plugin architecture that allows platform providers to easily write integrations for Kalabox.
Some sort of standard spec around what these should look like would be good. The plugin should define what the underlying docker architecture for that provider looks like, where the docker assets are stored, how they connect, etc. The plugin should also provide some information on how the integration with the https://github.com/fluxsauce/switchboard will be handled.
First pass at relevant things that should be contained:
some sort of standard "container definition"
some sort of standard "network definition that links the containers together"
some sort of standard "switchboard" definition that defines relevant switchboard things
@substack this is probably the biggest blocker for me right now but will definitely require some more work on my end before you can start doing relevant things.
We need to define a plugin architecture that allows platform providers to easily write integrations for Kalabox.
Some sort of standard spec around what these should look like would be good. The plugin should define what the underlying docker architecture for that provider looks like, where the docker assets are stored, how they connect, etc. The plugin should also provide some information on how the integration with the https://github.com/fluxsauce/switchboard will be handled.
First pass at relevant things that should be contained: