<story><title>JupyterHub 1.0</title><url>https://blog.jupyter.org/announcing-jupyterhub-1-0-8fff78acad7f</url></story><parent_chain><item><author>coleifer</author><text>When would someone use jupyterhub? I&amp;#x27;ve been running my own notebook server for years, but it&amp;#x27;s single-user, single machine. Is hub for like providing separate jupyterlab instances for a bunch of different users&amp;#x2F;different machines?</text></item></parent_chain><comment><author>jabl</author><text>We have it setup at work, as an alternative way to use our HPC resource compared to the traditional Linux shell + slurm usage.&lt;p&gt;User goes with the web browser to our jupyterhub URL, logs in with our usual credentials, selects a job type (amount of memory and max duration), and jupyterhub takes care of launching a jupyter kernel as a slurm batch job on a compute node in the cluster, and proxies http I&amp;#x2F;O via the jupyterhub node to the user web browser. In the jupyter notebook, users have access to the same cluster filesystems as if she would login traditionally via ssh.</text></comment>
<story><title>JupyterHub 1.0</title><url>https://blog.jupyter.org/announcing-jupyterhub-1-0-8fff78acad7f</url></story><parent_chain><item><author>coleifer</author><text>When would someone use jupyterhub? I&amp;#x27;ve been running my own notebook server for years, but it&amp;#x27;s single-user, single machine. Is hub for like providing separate jupyterlab instances for a bunch of different users&amp;#x2F;different machines?</text></item></parent_chain><comment><author>rhizome31</author><text>Yes exactly. At my work when a new scientist joins us we just create an account and she can get started on her research within minutes. Each user gets a contained environment in which we mount a disk of shared data.</text></comment>