(configuration-overview)=
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:
- {ref}
Jupyter's common configuration system <configure-common>- {ref}
Jupyter Server <configure-jupyter-server>- {ref}
Notebook extensions <configure-nbextensions>
Let's look at highlights of each area.
(configure-common)=
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.
(configure-jupyter-server)=
The Jupyter Server runs the language kernel and communicates with the front-end Notebook client (i.e. the familiar notebook interface).
Configuring the Jupyter Server
To create a
jupyter_server_config.pyfile in the.jupyterdirectory, with all the defaults commented out, use the following command:$ jupyter server --generate-configRelated: Configuring a language kernel to run in the Jupyter Server enables your server to run other languages, like R or Julia.
(configure-nbextensions)=
The Notebook frontend can be extending with JupyterLab extensions.
See the {ref}Frontend Extension Guide <frontend-extensions> for more information.
Security in Jupyter notebooks: 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.