Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Configuration File command line argument
See original GitHub issueUbuntu 18.04 + Locust 1.0.1 Configuration File
with 2 config files in current folder:
locust.conf
master.conf
locust --config=master.conf
always use locust.conf, not master.conf
Not sure if it’s by design…?
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Command line parameters or configuration file?
Command line parameters are useful for quickly overriding some parameter setting from the configuration file. As well, command line ...
Read more >Forget command-line arguments: use a config file | Medium
In this article, I'll show you ready-to-go examples of how moving your hyper-parameter selections, command-line arguments, and default options ...
Read more >Command Line Arguments and Config file
Command Line Arguments and Config file. Command line arguments are used to start various systems that can run on both the server and...
Read more >Command Line and Configuration File Syntax
The Batch Client can be used with the command-line parameters in Command Line Parameters and Configuration File Keys. Bracketed values ( [ ]...
Read more >Command-line parameters
Command -line parameters · -? · -c file — use an alternative configuration file instead of a default file. · -e file —...
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 Free
Top 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
Yep, layered configs are super useful! Just want to add to Lars answer. I use following in single config:
I.e. if an option defined more than once, the last value is be used. It can come from inherited or same config file.
Again, no need to remove anything. But definitely need to add clarification to docs. And about special headless flag too.
One more questions still: I assume, the config inheritance is: defaults -> ~/locust.conf -> ./locust.conf -> cmd args Is it correct?
Lars, Super! Could somebody add + clarify it here, please? Specifically, 2nd paragraph.