organization chart for rocker image universe

[Pit-Storm]

Hi Folks,

at first: Thank your for your great work! This saves a lot of time to us :-)

I was wondering where there is a organization chart which shows which image is made out of which other one. So that one can see, which to choose for the specific use case.

I know there had been one, but I'm not able to find it anymore.

Thanks for your help and kind regards :-)

[cboettig]

Is this what you are looking for? https://www.rocker-project.org/images/

Mostly it's the versioned stack that has a lot of vertical stacking. We're working on a way to make that both more transparent and more user-configurable.

[Pit-Storm]

Thank you @cboettig. I had in mind that I saw a image showing it as a chart for quick insight whichone to chose.

On the site you mentioned (which I was on already before) is said, that the shiny image is build on r-base. But as far as I know there is a version tag for shiny or especially for shiny-verse image. So as I understand there is a versioned shiny branch which has extending images.

Can you point out in which of your images rstudio(-server) and shiny(-server) is included or can be included via BUILD ARG? (Possibly this is the question I origionally want to answer)

Thank you! :-)

[cboettig]

@Pit-Storm yeah, good catch, the info for shiny is out of date.

• rocker/shiny is built on rocker/r-ver, rocker/shiny-verse extends rocker/shiny 'manually'. You can see all this just by looking at the Dockerfile for the image e.g, https://hub.docker.com/r/rocker/shiny-verse/dockerfile, though I know it's not great.

• The rocker versioned stack has the ability to add shiny-server to the instances that already have rstudio server: https://github.com/rocker-org/rocker-versioned/tree/master/rstudio#add-shiny-server-on-start-up-with-e-addshiny So this applies to rocker/rstudio and up that stack (tidyverse, verse, geospatial, ml, binder).

As you can probably tell, both of these examples (adding tidyverse to the shiny stack, adding shiny to the r-ver / rstudio stack) show the limits of the current vertical stack that we're trying to address with a more modular build system in the (work in progress!) stuff over at https://github.com/rocker-org/rocker-versioned2. The plan is for that to come with some new documentation etc to also make this a bit less of a pain to figure out than it is currently.

unfortunately the covid-19 thing isn't helping our development effort at this time, but stay tuned.

[Pit-Storm]

Thanks for that great answer. Now it is completly clear. I will check the versioned2 repo for further insights what is coming soon. Do you mind for contribution in that (ewrly) stage of that repo?

…

Am 27.03.2020 um 17:36 schrieb Carl Boettiger ***@***.***>:  @Pit-Storm yeah, good catch, the info for shiny is out of date. rocker/shiny is built on rocker/r-ver, rocker/shiny-verse extends rocker/shiny 'manually'. You can see all this just by looking at the Dockerfile for the image e.g, https://hub.docker.com/r/rocker/shiny-verse/dockerfile, though I know it's not great. The rocker versioned stack has the ability to add shiny-server to the instances that already have rstudio server: https://github.com/rocker-org/rocker-versioned/tree/master/rstudio#add-shiny-server-on-start-up-with-e-addshiny So this applies to rocker/rstudio and up that stack (tidyverse, verse, geospatial, ml, binder). As you can probably tell, both of these examples (adding tidyverse to the shiny stack, adding shiny to the r-ver / rstudio stack) show the limits of the current vertical stack that we're trying to address with a more modular build system in the (work in progress!) stuff over at https://github.com/rocker-org/rocker-versioned2. The plan is for that to come with some new documentation etc to also make this a bit less of a pain to figure out than it is currently. unfortunately the covid-19 thing isn't helping our development effort at this time, but stay tuned. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.