You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding the accessing of the Orca server using plotly.io when it's ran as a separate deployment on a Kubernetes setup. How would you typically configure the communication from any typical "singleuser" notebook to the externally running Orca server?
Context:
I'm currently working on a Kubernetes deployment of JupyterLab using the Zero-to-JupyterHub guide. Running plotly orca in a separate deployment would reduce the singleuser image size and complexity quite a bit and keep things neatly compartmentalized. Otherwise each and every singleuser container would contain a complete xvfb install!
The text was updated successfully, but these errors were encountered:
You're right that getting Orca running on a headless system can be tricky and it is much simpler/cleaner to have it run in its own container.
I'm not familiar with our tools in JupyterLab at the moment so I don't know how to call an externally running Orca server but I imagine it should be simple to do.
@TiemenSch it will be possible to call an externally running Orca in the next release of plotly.py (it should be in 4.3.0). See PR plotly/plotly.py#1850 for details!
I have a question regarding the accessing of the Orca server using
plotly.io
when it's ran as a separate deployment on a Kubernetes setup. How would you typically configure the communication from any typical "singleuser" notebook to the externally running Orca server?Context:
I'm currently working on a Kubernetes deployment of JupyterLab using the Zero-to-JupyterHub guide. Running plotly orca in a separate deployment would reduce the singleuser image size and complexity quite a bit and keep things neatly compartmentalized. Otherwise each and every singleuser container would contain a complete xvfb install!
The text was updated successfully, but these errors were encountered: