The following are tools and technologies that mybinder.org uses. You should have a working familiarity with them in order to make changes to the mybinder.org deployment.
This is a non-exhaustive list. Feel free to ask us questions on the gitter channel or here if something specific could be clearer!
MyBinder.org currently runs on Google Cloud. There are two Google Cloud projects that we use:
binder-staging contains all resources for the staging deployment
binder-staging
binder-prod contains all resources for the production deployment
binder-prod
We’ll hand out credentials to anyone who wants to play with the staging deployment, so please just ask!
While you only need merge access in this repository to deploy changes, ideally you should also have access to the two Google Cloud Projects so you can debug things when deployments fail.
We heavily use Kubernetes for the mybinder.org deployment, and it is important you have a working knowledge of how to use Kubernetes. Detailed explanations are out of the scope of this repository, but there is a good list of tutorials. Specifically, going through the interactive tutorial to get comfortable using kubectl is required.
kubectl
We use helm to manage our deployments, and it is important you have a working knowledge of how to use helm. Detailed explanations are out of the scope of this repository, but docs.helm.sh is an excellent source of information. At a minimum, you must at least understand:
We use Travis CI for doing all our deployments. Our .travis.yml file contains the entire configuration for our deployment. Travis CI has documentation on the various components of the .travis.yml file.
.travis.yml