The "mybinder.org, deconstructed" guide

Binder discuss
2

Yeah, I think separate app is definitely the way to go. In the same way that mybinder.org is a web service built on repo2docker’s cli, this would be a local gui app built on repo2docker, consuming its api (could be via cli or python).

When dealing with ephemeral cloud resources, pushing to a private registry is probably sensible to include, so you can build once and run several times. I’d almost call this a “mybinder.org, deconstructed” guide. It’s everything Binder does, but taken as more manual steps on your own terms:

  1. request cloud resources
  2. build image with repo2docker (requires installing docker)
  3. store image in a registry for future use (requires registry credentials; docker login being the easiest)
  4. launch a container from the image
  5. connect to the running notebook (might require cloud firewall configuration)
1 Like