Repo2docker-action: Brainstorming: CodeSpaces Instructions

thanks for putting this on the radar - how does codespaces differ from something like Binder? Does it only allow for vscode, or other interfaces as well?

Good question Codespaces allows for any arbitrary Dockerized web application to run on any port in addition to VSCode. My preferred way of using it for example will be serve Jupyter Lab on it 🎉

I think Binder has more generous compute at the moment than the free version of CodeSpaces but that might change

A general thought here - I think that we should find ways to show how repo2docker can plug in to other ecosystems, be used in workflows out of Binder etc. To that extent I think it'd be great to see information about how to integrate with codespaces!

That said, I think we should also show some caution, because codespaces falls more into the category of "vendor products" and we generally don't want to show preference for one vs the other (e.g. codespaces / gitpod / colab / cocalc / codeocean / etc). That said, it's pretty neat that codespaces works with open standards like repo2docker, so it's definitely worth highlighting and recognizing - I'm not quite sure how to walk that line! 🤔🤔🤔

That's an interesting point! I was also contemplating using repo2docker to launch notebook VMs on the cloud of your choice, which can be useful for compute like GPUs or other heavy workloads where mybinder.org may not be appropriate? The challenge is that infrastructure isn't free so it also starts to skate in this vendor zone of integrating with the cloud providers (AWS, GCP, Azure).

That being said, I think as practical matter folks may find it interesting for example, some interest from @hugobowne to use while doing Dask training at conferences.

I opened a thread on discourse to solicit more thoughts and opinions

oh I think the general use-case of "repo2docker connected with XXX" is an awesome one to highlight. And agreed re: quickly spin up a docker container in the cloud that is powered by an environment you create with repo2docker, that'd be really cool (we've also nibbled around a similar idea that uses the littlest jupyterhub so you can create a quick hub w/ an environment that was defined with repo2docker files)

I think that in the medium-term, I'll feel more comfortable with highlighting repo2docker in a particular vendor's ecosystem if we can also put it alongside repo2docker's use across a lot of other ecosystems (some vendor, some not) as well

I'll close this issue thanks it was helpful to gather ideas etc from this