Skip to content
This repository has been archived by the owner on Oct 26, 2019. It is now read-only.

Initial implementation #1

Closed
4 tasks done
parente opened this issue Dec 7, 2015 · 5 comments
Closed
4 tasks done

Initial implementation #1

parente opened this issue Dec 7, 2015 · 5 comments
Assignees

Comments

@parente
Copy link
Member

parente commented Dec 7, 2015

The initial implementation should have the following properties

Other issues will be opened about follow-on features.

@parente
Copy link
Member Author

parente commented Dec 8, 2015

Continuation of jupyter/dashboards#135. Related to jupyter/dashboards#105 and jupyter/dashboards_bundlers#3.

@dalogsdon
Copy link
Contributor

The initial implementation can be found in PR #5

fetch code from colocated notebook file on start (configurable path on disk)

Currently it will read notebook files placed in the data directory in the root of the project. This needs to be updated to read from a configurable path.

use jupyter-js-services and jupyter-js-output-area, not thebe

Done

filters all but comm channel messages from the frontend

Not done

supports one or more frontend browser client connections at a time and properly

Have not done testing on this, but should support multiple connections due to its simplicity. There is no concept of users at the moment, so all notebooks files in the data directory are accessible by anyone.

Do we want to create new issues for the remaining work in these tasks or keep working in this issue until all are complete? I expect each could build up a discussion, especially filtering and multi-user.

@parente
Copy link
Member Author

parente commented Dec 15, 2015

Do we want to create new issues for the remaining work in these tasks or keep working in this issue until all are complete? I expect each could build up a discussion, especially filtering and multi-user.

If filtering is implementable atop what exists here, that's enough for the moment and we can open a follow-on about comm channel only.

We don't need anything special for authorization for multiple users, just need to make sure the server is non-blocking across users. Authentication is already issue #4.

@dalogsdon
Copy link
Contributor

Added config for notebook directory location. We will close this issue and continue work in other issues as discussed in previous comments.

@parente
Copy link
Member Author

parente commented Jan 4, 2016

Feel free to modify the issues too to better fit how you want to chunk up the work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants