Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify what it means to deploy a "Data8 style hub" #785

Open
sgibson91 opened this issue Dec 8, 2023 · 6 comments
Open

Clarify what it means to deploy a "Data8 style hub" #785

sgibson91 opened this issue Dec 8, 2023 · 6 comments

Comments

@sgibson91
Copy link
Member

Context

Every now and then, I am asked to deploy a hub with a "Data8 style" image and, as an engineer who was never involved in that project, it holds no meaning for me.

2i2c have started moving towards using upstream, community managed images (such as scipy-notebook and rocker) for user images, and away from the previous in-house maintained image, so there isn't really a "default" image that we deploy.

If we are going to be selling "Data8 style" hubs, we should defined exactly which image (or set of images) we mean when we say that, to reduce the back and forth between engineering and partnerships regarding what actually needs to be deployed.

Proposal

No response

Updates and actions

No response

@GeorgianaElena
Copy link
Member

YES!!!! This also confuses me!

@colliand
Copy link
Contributor

colliand commented Dec 8, 2023

Good to know! I'd like us to build a menu of "standard images" to eliminate this confusion. I'd also like to build a form so that hub launch specs are collected in a structured format. I've started investigating that with AirTable.

@sgibson91
Copy link
Member Author

sgibson91 commented Dec 8, 2023

So I think two standard images we've adopted are jupyter/scipy-notebook and rocker/r-binder for python and R environments separately. We have forks of both these in 2i2c-org GitHub that additionally include nbgitpuller until that package is added upstream. Note that both of these images are managed by communities external to 2i2c (but there may be overlap and we should provide some labour to help since we depend on them, but that's a different discussion).

@damianavila
Copy link
Contributor

So I think two standard images we've adopted are jupyter/scipy-notebook and rocker/r-binder for python and R environments separately. We have forks of both these in 2i2c-org GitHub that additionally include nbgitpuller until that package is added upstream.

I would encourage using these ones ⬆️ instead of the cloudbank-specific image (which is pretty similar given it is inherited from the scipy-notebook as well, IIRC) given some recent customizations they had (that might be problematic for others): 2i2c-org/cloudbank-data8-image#5

@colliand
Copy link
Contributor

It will be helpful for 2i2c to develop a catalog of images. What images does 2i2c use? For which audiences?

@jmunroe
Copy link
Contributor

jmunroe commented Dec 11, 2023

The images currently available on showcase.2i2c.cloud are the ones I've been suggesting to communities as a starting point:

image

In January, we plan on developing guides/tutorials on how to customize these community-maintained base images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants