Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #134 #135

Merged
merged 1 commit into from
Dec 14, 2019
Merged

Fixes #134 #135

merged 1 commit into from
Dec 14, 2019

Conversation

krinsman
Copy link
Contributor

Fixes #134

Compare jupyter/notebook#5021 which fixes notebook's #5002 jupyter/notebook#5002

@krinsman
Copy link
Contributor Author

krinsman commented Nov 5, 2019

Instead of deleting lines 1157 and 1158 in serverapp.py (i.e. those which over-ride the user-specified values of the root directories for the content and kernel managers) an alternative approach would be to make the root directories of the content and kernel managers non-configurable. (This is implemented by the force push.) Both fix #134

Either way users' configurations will not be silently over-written.

…r get the application option as part of calculating the default
@krinsman
Copy link
Contributor Author

krinsman commented Dec 3, 2019

Updated PR to fit with the solution which was ultimately merged into notebook
jupyter/notebook#5021

@Zsailer Zsailer merged commit 7d2fe81 into jupyter-server:master Dec 14, 2019
@Zsailer
Copy link
Member

Zsailer commented Dec 14, 2019

Thanks, @krinsman. This looks right.

Zsailer added a commit to Zsailer/jupyter_server that referenced this pull request Nov 18, 2022
* allow ports to be configured

* Bump to 0.12.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

root_dir for Contents Manager not loaded from config file
2 participants