iDmple
commented
3 years ago Just to clarify,
This automatic app deployment for now just supports the provided Dockerfile template. There is no notebook support for now in the HIP.
One repository must be created per app, and the Dockerfile should specify the app executable to run. There is an option if we must run a shell.
Your usecase seems much more complex, and probably the app template won't work as it is. Should we organize a meeting to discuss your needs in detail?
maedoc
@i-Zaak feel free to expand, but we should create a set of issues to track the different stuff we'll add here
For each, we could assume we're running a notebook server (w/ embedded Firefox or nteract instance if that's useful for the nextcloud app framework) and that the workflow represented is just a notebook being executed there. VS Code has good support for Jupyter notebooks so that's anther visual frontend to the workflow which would be appropriate if there's a lot of coding to do. It's a marginal increase in image size so having all the tools available is fine too.
For the ensemble of images, we can follow what we've done before: create a large base image with the toolset, then a series of layers on top for each concrete app, perhaps finally a dev image for debugging or writing next/new workflows. We could also just package it all into a singe tvb image and then the user chooses what to do in the notebook interface.