[Feature Request] Support for DASH_HOST / DASH_PORT as environment overrides
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem? Please describe.
I'd like to be able to set DASH_HOST/DASH_PORT as environment variables to exclusively control the listen address for the dash server. HOST/PORT are too generic and collide with other services running on the same environment.
Describe the solution you'd like
Support DASH_HOST and DASH_PORT in addition to HOST and PORT, preferring DASH_HOST/DASH_PORT if they're provided.
Describe alternatives you've considered
I don't see any.
Additional context
From looking at https://github.com/plotly/dash/pull/1134 it seems like the intention was to name this environment variable DASH_HOST, but for some reason it was implemented as just HOST. Not sure if this was a mistake but we probably can't remove support for HOST without a breaking change.
Contributor guide
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 environment-variable handling introduced in pull request #1134 and locate the existing HOST/PORT support in the Dash server. Done means DASH_HOST and DASH_PORT take precedence when set while the existing HOST and PORT variables continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100