Beyond the default configuration settings, you can configure a rich array of options to suit your workflow. Here are areas that are commonly configured when using Jupyter Notebook:
Jupyter's common configuration system <configure_common>Notebook server <configure_nbserver>Notebook front-end client <configure_nbclient>Notebook extensions <configure_nbextensions>
Let's look at highlights of each area.
Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process for creating a configuration file and editing settings is similar for all the Jupyter applications.
- Jupyter’s Common Configuration Approach
- Common Directories and File Locations
- Language kernels
- traitlets provide a low-level architecture for configuration.
The Notebook server runs the language kernel and communicates with the front-end Notebook client (i.e. the familiar notebook interface).
Configuring the Notebook server
To create a
jupyter_notebook_config.pyfile in the.jupyterdirectory, with all the defaults commented out, use the following command:$ jupyter notebook --generate-config
Command line arguments for configuration <config>settings are documented in the configuration file and the user documentation.Running a Notebook server <working_remotely>- Related: Configuring a language kernel to run in the Notebook server enables your server to run other languages, like R or Julia.
How front-end configuration works <frontend_config>Example: Changing the notebook's default indentation setting <frontend_config>Example: Restoring the notebook's default indentation setting <frontend_config>
Persisting configuration settings <frontend_config>
Security in Jupyter notebooks: <notebook_security> Since security policies vary from organization to organization, we encourage you to consult with your security team on settings that would be best for your use cases. Our documentation offers some responsible security practices, and we recommend becoming familiar with the practices.