Considering adding support for env variables
See original GitHub issueHi, I was playing with distributed and for both dask-worker and dask-scheduler you have to specify an IP:PORT (generally).
Considering the use with docker images and containers I think it would be useful to use also env variables.
Would you consider to add something like:
DASK_WORKER_IP=your_ip
DASK_WORKER_PORT=your_port
DASK_SCHEDULER_IP=your_ip
DASK_SCHEDULER_PORT=your_port
to specify them?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Environment Variables: What They Are and How To Use ...
Environment variables help you isolate critical application configuration data using env files or remote variable stores.
Read more >Consider adding --env-from-secret or support for setting ...
There is no current way to run a job via kubectl run that allows setting the values of environment variables via secrets. What...
Read more >An Introduction to Environment Variables and How to Use ...
Multiple environment variables are supported by specifying more than one --env option in the webpack command. These are referenced in webpack ...
Read more >5 reasons why your .env environment variables don't work
5 reasons why your .env environment variables don't work · 1. Your framework doesn't automatically load .env files. · 2. You added or...
Read more >Introduction to environment variables
Secrets masking provides added security within CircleCI by obscuring ... The value of the environment variable or context will not be masked in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In my general experience, ENV variables should take precedence over the config file variables. CLI should take precedence over both.
So: cli > env > conf