How to delete obsolete binder repo

[garej]

Please, add information how to delete a binder image if needed (or at least provide such information in tutorial of FAQ). Will it delete automatically if initial repository is deleted?
Thanks!

[betatim]

From @minrk in gitter this is the information for making an image inaccessible or if you need it have removed:

If you accidentally push something that shouldn't be there, you'll need to ask us to take it down.
If you remove the commit from your repo, however, outside users won't be able to get at it
Since Binder resolves refs with the storage provider (e.g. GitHub) before building or launching the image. So if a commit is pulled from the repo, Binder won't launch it even if a build of that commit is in the cache. So that information might be available to us, the Binder operators, until the cache is cleared, you are in total control of whether it's available to the public

Maybe we can/should add to this an entry about mybinder.org being a free public service without auth that only has access to things which are already public. An "abuse" vector that could become tedious is that people briefly make their repository public, use it on mybinder.org and then request us to delete the image because really they want their repo to be secret. Currently this doesn't seem to happen but if the number of requests for deletion shoots up I think we should specifically exclude that kind of behaviour as it is against the spirit of mybinder.org.

I think the place to add this would be a new file in https://github.com/jupyterhub/binder/tree/master/doc/howto. Do you want to create a PR for that @garej ?

[garej]

@betatim, Thanks for prompt reply. You should definitely add this to the documentation somewhere as, to my mind, there is a good style for any software to provide somewhat similar to "uninstall" section.
When it comes to my case, I need a sort of a 'testbed' option, because I'm not sure how my interactive functionality is going to be working on binder. I would want to delete it myself if I'm not satisfied with result of deployment, not because I want to abuse the rules and ideology of the project itself.

[betatim]

When it comes to my case, I need a sort of a 'testbed' option, because I'm not sure how my interactive functionality is going to be working on binder. I would want to delete it myself if I'm not satisfied with result of deployment, not because I want to abuse the rules and ideology of the project itself.

For testing you can give http://repo2docker.readthedocs.io/ a go. This is the tool we use to build the repo. You can run it locally and get faster turn around times, more logs and it is all private to your machine.

I think for your case removing the commits from your git repository is the self-service way forward. It means the images on mybinder.org will become inaccessible to members of the public. If that isn't good enough I'd recommend against using mybinder.org for trialling things and use repo2docker only.

Do you want to make a PR that adds to the FAQ?

[garej]

@betatim, I see, thank you. Concerning pull request, why not, it's a good idea. Should I do it?

[betatim]

Concerning pull request, why not, it's a good idea. Should I do it?

That would be great and help us out.

Let's keep this issue open till we have a PR that implements this so it doesn't get forgotten.

[meeseeksmachine]

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/deleting-a-binder-deployment/7247/1

[MdWitte]

From @minrk in gitter this is the information for making an image inaccessible or if you need it have removed:

If you accidentally push something that shouldn't be there, you'll need to ask us to take it down.
If you remove the commit from your repo, however, outside users won't be able to get at it
Since Binder resolves refs with the storage provider (e.g. GitHub) before building or launching the image. So if a commit is pulled from the repo, Binder won't launch it even if a build of that commit is in the cache. So that information might be available to us, the Binder operators, until the cache is cleared, you are in total control of whether it's available to the public

Hi, how can I contact you guys to take down a specific repo? I could not find an email adress anywhere, except security@ipython.org. Thank you in advance!

[betatim]

To make your repository (or a commit in it) inaccessible you can remove that commit from the repository.

Which commit from which repository would you like to have removed?

[MdWitte]

Thank you very much for the quick reply! I already deleted the entire repository from my account, but if possible I would like you to take it down from mybinder.org as well. The repo is https://github.com/MdWitte/Dashboard-V1

[betatim]

Done

[mkotsovoulou]

I would like you to take it down my repo from mybinder...
I published everything by mistake: https://github.com/mkotsovoulou
I can not find a was to delete my account on your website... Thank you...

[minrk]

@mkotsovoulou mybinder.org doesn't have accounts, or store anything beyond a cache of builds for repos. Any public repo on the internet can be loaded through mybinder.org by anyone, and anything no longer public cannot be loaded through mybinder.org, so to remove a repo from mybinder.org, you can make it private on GitHub, etc. To remove a commit it should be sufficient to rewrite your git repo's history (if the commit is still accessible via GitHub, it will still be accessible on mybinder.org). I can purge the build cache for your repos, if that would help you.

If you'd like us to 'ban' your GitHub account to prevent anyone from building or launching your repos, we can do that, too.