Add a CLI param to override config variables
See original GitHub issueSomething like -c https.enable=true
.
This would remove the need to have ip/port/public/private params.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Add a CLI param to override config variables · Issue #419 - GitHub
Something like -c https.enable=true. This would remove the need to have ip/port/public/private params. ... Add a CLI param to override config variables #419....
Read more >How do I override Git configuration options by command line ...
Quoting from kernel.org/pub/software/scm/git/docs -c <name>=<value> Pass a configuration parameter to the command. The value given will override values from ...
Read more >Environment variables to configure the AWS CLI
If you specify an option by using a parameter on the AWS CLI command line, it overrides any value from either the corresponding...
Read more >CLI Arguments with Environment Variables - Typer - tiangolo
Try: How can I terminate a program? How to launch applications? How to add help to CLI argument? Hi there Ask our docs!...
Read more >config Declarations: command-line overrides - chapel-lang.org
Configuration variables are variables whose default values can be overridden on the executable's command-line. Here's a simple example:.
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
The thing is: at the moment the parameters are not working correctly. For example:
lounge start --port 1234
orlounge start -P 1234
starts Lounge on default port 9000. Same withlounge --port 1234 start
(That’s the waylounge -h
describes the usage) To make it work you have to dolounge --port 1234
,lounge -- start --port 1234
orlounge -- --port 1234 start
which is not the way it should be, I think. The whole CLI params parsing implementation has a problem.Should the ip/port/public/private params be removed in the same PR? I’ll look into this issue.