JupyterHub is a good idea, but then the authentication and spawners are
little complex to implement i guess.
On Wednesday, March 21, 2018 at 4:49:53 PM UTC-4, Paul Hobson wrote:
>
> Rockssk,
>
> I think JupyterHub can handle parts 1 and 3:
> https://github.com/jupyterhub/jupyterhub
>
> I'm not
Thanks Paul for your suggestion,
here is what we are planning now, to have a seperate notebook server per
venv/project and let all developers within the project to access the same
notebook server, will look at the kernel.json .
On Wednesday, March 21, 2018 at 5:29:00 PM UTC-4, Michael
For #2 it depends on how complex your dependencies are, but in general
making each virtual environment available as a Jupyter kernel should do
what you want. Hint: you'll want to edit the "kernel.json" files to give
them descriptive names for the UI!
On Wed, Mar 21, 2018 at 3:49 PM, Paul Hobson
Rockssk,
I think JupyterHub can handle parts 1 and 3:
https://github.com/jupyterhub/jupyterhub
I'm not sure about your needs for 2, though.
-paul
On Wed, Mar 21, 2018 at 1:42 PM, rockssk wrote:
> All,
>
>we have multiple python projects going on currently , each have
All,
we have multiple python projects going on currently , each have their
own virtual environment and maintain the dependant packages/libraries
within the venv
We are looking for a solution where
1. Multiple developers can login at the same time into a central
notebook app,