lincc-frameworks / lincc-frameworks/lsdb-benchmarking
Support running the dashboard in Remote Jupyter Environments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Plotly dash supports running in Jupyter, and this works for the lbench dash running in a local Jupyter notebooks, but in remote environments like RSP there are issues about requests to different ports and different protocols (http vs https). I tried having a look at setting up a proxy in environments like that in the Sean/jupyter branch, but couldn't figure out how to correctly setup the forwarding and also have plotly generate the URLs for its resources to follow that proxy.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing dashboard's Jupyter integration and the Sean/jupyter branch mentioned in the issue, then reproduce the behavior in a remote environment such as RSP. Trace the proxy forwarding and generated resource URLs across HTTP and HTTPS; done means the dashboard runs remotely and its requests and resources follow the proxy correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, plotly, python
- Domain
- networking, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100