-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
remove base_kernel_url #5100
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
remove base_kernel_url #5100
Conversation
The term 'kernel server' in a docstring suggests that at one point we were considering that kernels could be handled by a different webserver from the notebooks. Was that ever the case? I don't remember hearing any discussion of it. |
I think it probably was to handle the case of kernels running on a On Wed, Feb 12, 2014 at 4:15 PM, Thomas Kluyver [email protected]:
Brian E. Granger |
And because of the new URL scheme, a proxy can send /api/kernels to a different server anyway, so I don't think the separate configurable solves a problem. Related: Can we also get rid of ws_url, or no? |
Hmm, I don't actually remember the details is ws_url - will have to look Sent from my iPhone
|
It's the same as base_kernel_url - a separate URL, so that the websockets can be on another host. Never used, and can also be handled in the server via a proxy. |
I don't see any problem with getting rid of ws_url. |
The removal of |
@minrk will remove |
remove base_kernel_url
While we are simplifying base_project_url to base_url, base_kernel_url has never been documented, and has only ever been confusing. In every case I have seen, base_kernel_url should be identical to base_url, so this just removes the separate configuration value.
I would also like to consider getting rid of ws_url, unless someone can make a case for why it should be kept.
closes #5099