Hello world!

welcome to WordPress. This is your first post. Edit or delete it, then start writing!

Running a public notebook server

Don’t run a public notebook server unless you first secure it with a password and SSL/HTTPS as described above

By default the notebook server only listens on the localhost/ network interface. If you want to connect to the notebook from another computers, or over the internet, you need to configure the notebook server to listen on all network interfaces and not open the browser. You will often also want to disable the automatic launching of the web browser.

This can be accomplished by passing a command line options.

jupyter notebook --ip=* --no-browser

You can also add the following to your jupyter_notebook_config.py file:

c.NotebookApp.ip = '*'
c.NotebookApp.open_browser = False

Running with a different URL prefix

The notebook dashboard typically lives at the URL http://localhost:8888/tree. If you prefer that it lives, together with the rest of the notebook web application, under a base URL prefix, such as http://localhost:8888/ipython/tree, you can do so by adding the following lines to your jupyter_notebook_config.py file.

c.NotebookApp.base_url = '/ipython/'
c.NotebookApp.webapp_settings = {'static_url_prefix':'/ipython/static/'}

Using a different notebook store

By default, the notebook server stores the notebook documents that it saves as files in the working directory of the notebook server, also known as the notebook_dir. This logic is implemented in theFileNotebookManager class. However, the server can be configured to use a different notebook manager class, which can store the notebooks in a different format.

The bookstore package currently allows users to store notebooks on Rackspace CloudFiles or OpenStack Swift based object stores.

Writing a notebook manager is as simple as extending the base class NotebookManager. Thesimple_notebook_manager provides a great example of an in memory notebook manager, created solely for the purpose of illustrating the notebook manager API.

Known issues

When behind a proxy, especially if your system or browser is set to autodetect the proxy, the notebook web application might fail to connect to the server’s websockets, and present you with a warning at startup. In this case, you need to configure your system not to use the proxy for the server’s address.

For example, in Firefox, go to the Preferences panel, Advanced section, Network tab, click ‘Settings…’, and add the address of the notebook server to the ‘No proxy for’ field.

View the original notebook on nbviewer