xcube-dev / xcube-dev/xcengine
Consider a web interface to set parameters for server mode
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 8
Description
When running an xcengine container in server mode, parameters for user code have to be passed as arguments to the Docker image's entry point. In many deployment scenarios, this may not be practical.
Idea: add an option for server mode whereby the server and viewer aren't started at once. Instead, a single-page web configuration interface comes up, allowing the user to set the parameters before running the notebook code and starting the server.
Could also provide a REST endpoint for the same purpose, though I'm not sure that there's a compelling use case for that.
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
No files, tests, or entry points are named. Start by tracing the Docker image's server-mode entry point and how it starts the server, viewer, and notebook code; define the configuration flow and completion criteria before assessing whether a REST endpoint belongs in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, jupyter-notebook, python
- Domain
- backend, devops, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100