💨 💨 The Binder Project is moving to a new repo. 💨 💨
📚 Same functionality. Better performance for you. 📚
Over the past few months, we've been improving Binder's architecture and infrastructure. We're retiring this repo as it will no longer be actively developed. Future development will occur under the JupyterHub organization.
- All development of the Binder technology will occur in the binderhub repo
- Documentation for users will occur in the jupyterhub binder repo
- All conversations and chat for users will occur in the jupyterhub binder gitter channel
Thanks for updating your bookmarked links.
💨 💨 The Binder Project is moving to a new repo. 💨 💨
Scripts for creating preconfigured Binder clusters with one command
npm install binder-launch
Launching a Binder cluster on GCE is the easiest way to get started (and it's also the way Binder is running in production). Any Binder deployment will require at least 3 small compute instances, which can get expensive if left running -- before launching the cluster, verify that the resources being created match your budget.
binder-launch contains a script that will configure a complete Binder cluster on
Google Compute Engine. To use this script:
- Create an account on GCE, make a new project and ensure billing is set up correctly for that project. We'll assume this project is called 'binder-project' in the rest of the instructions
- Initialize Google Compute Engine for the new project
- Download the
gcloudutility by following the instructions here - Log into the GCE service:
gcloud init gcloud config set project binder-project
npm run launch
The utility should prompt you for cluster configuration information during the launch process
WARNING: the script will output how many compute instances it is creating, so be sure to understand the estimated monthly cost of that cluster before leaving it running
npm run destroy
WARNING: check the resources that exist in your project after the destroy command has been run, just in case...