Support for Flavors about arkitekt HOT 3 OPEN

Regarding the config.yaml I was wondering if my docker-params should be part of a docker-compose file instead. This would make it easier to understand because it's documented familiarly and we could use all docker-compose features.

One of the things that we would have to figure out regarding different container technologies is the "translation" of these parameters. Passing the right drivers and devices looks different depending on the combination of device and container.

We could probably make these part of the app's features. So only if you have defined the parameters for singularity the app supports running with singularity. I like a more automatic approach but I couldn't find a translation between docker-compose and singularity-compose (which I have never tried before but could be the alternative configuration file).
Other parameters such as port forwards for access to jupyter-notebooks would probably handle a bit easier but I am not sure if there aren't problems with automatic translation of the parameters as well.

from arkitekt.

Cool Stuff!

I actually do feel that the selectors would be the place for having this sort of configuration, but utilizing an interface like
approach where the selectors would be an abstract mapping that specific backends could implemement their run calls in.
Something like that:

This would allow us to use the same selectors for different backends and also would allow us to have the smae codebase for the arkitekt cli (using the helper library to call a configured backend (by default docker, but maybe also podman), and for port or the conceptualize cluster app? What do you think?

from arkitekt.

I think this would also work and I like it more in the sense that it would allow us to run multiple backends without having them depend on the configuration.

I am wondering how complicated it will get with all the different options but I guess this can be added one after another.
I would like to see port forwarding as well so we can do something like the following.

One of the "Apps" that I would like to build is an "explore in jupyter" which would run a jupyter-notebook, so you can use it to explore "intermediate" results. I think this would be a good counterbalance to having it fully automatized but still be interactive.

from arkitekt.