server, the official solution is JupyterHub. To use JupyterHub, you need a Unix server (typically Linux) running somewhere that is accessible to your users on a network. This may run over the public internet only by the current user. By default, this is located at: ~/.local/share/jupyter/nbsignatures.db # Linux ~/Library/Jupyter/nbsignatures.db # OS X %APPDATA%/jupyter/nbsignatures.db # Windows Each signature manager, npm. Alternatively, install both of these from your package manager. For example, on Ubuntu or Debian: sudo apt-get install nodejs-legacy npm You can then build the JavaScript and CSS by running:

[https://jupyterhub.readthedocs.io/en/latest/]. To use JupyterHub, you need a Unix server (typically Linux) running somewhere that is accessible to your users on a network. This may run over the public internet only by the current user. By default, this is located at: ~/.local/share/jupyter/nbsignatures.db # Linux ~/Library/Jupyter/nbsignatures.db # OS X %APPDATA%/jupyter/nbsignatures.db # Windows manager, npm. Alternatively, install both of these from your package manager. For example, on Ubuntu or Debian: sudo apt-get install nodejs-legacy npm You can then build the JavaScript and CSS by running:

segfault the Python interpreter: In [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (PR #3380) • Don’t trash files on different device to home dir on Linux (PR #3304) • Clear waiting asterisks when restarting kernel (PR #3494) • Fix output prompt when server, the official solution is JupyterHub. To use JupyterHub, you need a Unix server (typically Linux) running somewhere that is accessible to your users on a network. This may run over the public internet

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to

to segfault the Python interpreter: [5]: import sys from ctypes import CDLL # This will crash a Linux or Mac system # equivalent calls can be made on Windows # Uncomment these lines if you would like cookie on requests without cookie (3380) • Don’t trash files on different device to home dir on Linux (3304) • Clear waiting asterisks when restarting kernel (3494) • Fix output prompt when execution_count running code in your Jupyter session as you. However, some environments (like Windows Subsystem for Linux (WSL) and Chromebooks), launch- ing a browser using a redirect file can lead the browser failing to