{"action":"created","issue":{"url":"https://api.github.com/repos/binder-project/binder/issues/8","labels_url":"https://api.github.com/repos/binder-project/binder/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/binder-project/binder/issues/8/comments","events_url":"https://api.github.com/repos/binder-project/binder/issues/8/events","html_url":"https://github.com/binder-project/binder/issues/8","id":103329438,"number":8,"title":"API Design for binder resources","user":{"login":"rgbkrk","id":836375,"avatar_url":"https://avatars.githubusercontent.com/u/836375?v=3","gravatar_id":"","url":"https://api.github.com/users/rgbkrk","html_url":"https://github.com/rgbkrk","followers_url":"https://api.github.com/users/rgbkrk/followers","following_url":"https://api.github.com/users/rgbkrk/following{/other_user}","gists_url":"https://api.github.com/users/rgbkrk/gists{/gist_id}","starred_url":"https://api.github.com/users/rgbkrk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rgbkrk/subscriptions","organizations_url":"https://api.github.com/users/rgbkrk/orgs","repos_url":"https://api.github.com/users/rgbkrk/repos","events_url":"https://api.github.com/users/rgbkrk/events{/privacy}","received_events_url":"https://api.github.com/users/rgbkrk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-26T17:51:29Z","updated_at":"2015-08-26T18:09:56Z","closed_at":null,"body":"In order to use binder with thebe and other javascript frontends that use kernels directly, we'll want to expose a provisioning API. I've been imagining a higher order kernels provisioning API but generally what we want is two resources to work with in any case:\r\n\r\n* Building a binder from a repository\r\n* Launching a binder"},"comment":{"url":"https://api.github.com/repos/binder-project/binder/issues/comments/135127022","html_url":"https://github.com/binder-project/binder/issues/8#issuecomment-135127022","issue_url":"https://api.github.com/repos/binder-project/binder/issues/8","id":135127022,"user":{"login":"rgbkrk","id":836375,"avatar_url":"https://avatars.githubusercontent.com/u/836375?v=3","gravatar_id":"","url":"https://api.github.com/users/rgbkrk","html_url":"https://github.com/rgbkrk","followers_url":"https://api.github.com/users/rgbkrk/followers","following_url":"https://api.github.com/users/rgbkrk/following{/other_user}","gists_url":"https://api.github.com/users/rgbkrk/gists{/gist_id}","starred_url":"https://api.github.com/users/rgbkrk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rgbkrk/subscriptions","organizations_url":"https://api.github.com/users/rgbkrk/orgs","repos_url":"https://api.github.com/users/rgbkrk/repos","events_url":"https://api.github.com/users/rgbkrk/events{/privacy}","received_events_url":"https://api.github.com/users/rgbkrk/received_events","type":"User","site_admin":false},"created_at":"2015-08-26T18:09:56Z","updated_at":"2015-08-26T18:09:56Z","body":"## Launching a binder\r\n\r\nRight now this is part of the `GithubBuildHandler` as a GET on the `/apps/` resource. This piece could actually be distant from GitHub, relying only on image names (those that have been built, whitelisted, whatever). In the [Docker API](https://docs.docker.com/reference/api/docker_remote_api_v1.20/#create-a-container) (just as a reference), they `POST to /containers/create` with the payload.\r\n\r\nSince we're talking \"precanned\" images (in the sense they were built prior or already existing) that get launched either by a user visiting a resource or via AJAX call by JavaScript, I think we can pick a solid resource name. I'm tilted towards `spawn` since it's a noun and we've already been using it in tmpnb.\r\n\r\n\r\n\r\n\r\n\r\n\r\n"}}