+1 to retiring tmpnb. Let's not add features, especially since "popular" binders could expose "secret" gist repository, add complexity and require us to add state to binder.
On Dec 20, 2017 18:02, "Brian Granger" <elliso...@gmail.com> wrote: > Thanks for the update Min, this sounds like a good plan. What about > building a page on mybinder.org with featured or popular repos, and > just directly forward try.jupyter.org there? > > On Wed, Dec 20, 2017 at 7:54 AM, MinRK <benjami...@gmail.com> wrote: > > tmpnb.org powers https://try.jupyter.org, and is a lightweight service > for > > temporary notebook servers. However, tmpnb gets a lot less light as the > > number of users grows, and the scope of what we want to demo grows. Since > > tmpnb only allows serving a single repo, we’ve had to build an enormous > > kitchen-sink docker image with everything we want to demo. This is not > > sustainable, and keeping tmpnb.org up isn’t really working anymore. > With the > > new Binder up and running, there is a better avenue for demoing Jupyter > use > > cases that doesn’t require trying to build a one-size-fits-all demo. > > > > Our plan is to update the try.jupyter.org page to be a set of links to > > Binder repos demoing Jupyter, and shutdown the tmpnb.org service. This > will > > involve: > > > > creating a few binderable repos for demoing Jupyter > > making try.jupyter.org a landing page pointing to a few selected demo > repos > > on Binder > > shutting down tmpnb.org > > putting the docker-demo-images repo in the attic, since people who want > to > > demo their own work can now create Binders instead of adding to the big > demo > > image. > > > > See the GitHub Issue for further planning. > > > > We don’t have a timeframe for this yet, but if you are relying on > tmpnb.org > > for anything let us know. The odds are that Binder can already serve you > > better than tmpnb does right now. > > > > -Min > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Project Jupyter" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to jupyter+unsubscr...@googlegroups.com. > > To post to this group, send email to jupyter@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/jupyter/CAHNn8BUG% > 2BXR9BVLzoichdeWO34zXvwJ4GFTeirMMp84pa9UemA%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Brian E. Granger > Associate Professor of Physics and Data Science > Cal Poly State University, San Luis Obispo > @ellisonbg on Twitter and GitHub > bgran...@calpoly.edu and elliso...@gmail.com > > -- > You received this message because you are subscribed to the Google Groups > "Project Jupyter" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jupyter+unsubscr...@googlegroups.com. > To post to this group, send email to jupyter@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jupyter/CAH4pYpSjJdz1uae0Lgnwx2t7n0TxmtJh3Q3k2ej7qABhG0LB_Q%40mail. > gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscr...@googlegroups.com. To post to this group, send email to jupyter@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CANJQusWUWJE7ruBEb%2BSJxGGUNHs44N%2BdGff4aqFmTQGTUQqrQw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
