Redirect Tree view to Index.ipynb if it exists

[rgbkrk]

First pass on #181, adding an index page.

I've deployed this to qa and have two samples:

GitHub repository

http://qa2.nb.minrk.net/github/rgbkrk/index.ipynb/tree/master/

Gist with index.ipynb

http://qa2.nb.minrk.net/gist/rgbkrk/8653938

---

While testing this out, it seems like we don't have redirection to a tree enabled (have to know the magic behind nbviewer's URLs to list a repo). Am I missing something here?

[Carreau]

http://qa2.nb.minrk.net/gist/rgbkrk/8653938

gist with only one file show already this file by default :-)

[ellisonbg]

This works as expected. But I agree that we currently don't have a great
URL scheme that makes it easy for people to link to an entire repo. For
example, it would be nice if the following "just worked" when pasted into
our URL form on the home page:

• ipython = username
• ipython/ipython = username + repo

But that is a separate issue. I will open up one for that. Thanks for
working on this Kyle!

On Mon, Jan 27, 2014 at 11:25 AM, Matthias Bussonnier <
notifications@github.com> wrote:

http://qa2.nb.minrk.net/gist/rgbkrk/8653938

gist with only one file show already this file by default :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/182#issuecomment-33410960
.

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

[rgbkrk]

gist with only one file show already this file by default :-)

Yeah, this lets them have multiple files and their own index notebook.

Are people happy with this PR? I feel safe in merging, but don't want to step on toes.

[Carreau]

I would prefer to wait to sort how we should do in live notebook and dashboard to have uniform experience.

[ellisonbg]

Yes, based on our discussion at the dev meeting, I think we need a bit more
thought on this one. We will probably do something like this, but have a
few more details to work out. Let's wait and keep talking.

On Sun, Feb 2, 2014 at 10:53 AM, Matthias Bussonnier <
notifications@github.com> wrote:

I would prefer to wait to sort how we should do in live notebook and
dashboard to have uniform experience.

Reply to this email directly or view it on GitHubhttps://github.com//pull/182#issuecomment-33908506
.

Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger@calpoly.edu and ellisonbg@gmail.com

[ellisonbg]

Here is a PR on ipython/master that implements index.ipynb handling for the live notebook:

ipython/ipython#5001

Question @rgbkrk does this implementation handle all cases of index: index.ipynb, INDEX.ipynb, Index.ipynb?

[rgbkrk]

Yeah, this is case insensitive (I lowercase the actual filename to check). First* file that matches index.ipynb case insensitively wins. Index.ipynb, index.ipynb and InDeX.iPYnb all resolve properly.

[Carreau]

So you cannot force the view of the tree? And goodby seeing directory strucures and ipynb bellow like on github?

Envoyé de mon iPhone

Le 3 févr. 2014 à 03:31, "Brian E. Granger" notifications@github.com a écrit :

Here is a PR on ipython/master that implements index.ipynb handling for the live notebook:

ipython/ipython#5001

Question @rgbkrk does this implementation handle all cases of index: index.ipynb, INDEX.ipynb, Index.ipynb?

—
Reply to this email directly or view it on GitHub.

[rgbkrk]

So you cannot force the view of the tree? And goodby seeing directory strucures and ipynb bellow like on github?

No no, directory structures can still be seen.

This just gives people an option to create their own index rather than our directory view, by creating "index.ipynb".

[minrk]

we aren't going to redirect to index.ipynb for now.