-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config file support #1
Comments
Hi, I would like to do this. Do I need to make a small button that opens the file explorer or just specify the access path in plain text? |
Hi @MoskalykA, a small button that opens the file explorer would be great. I assigned this issue to you, thanks. |
I am setting the options according to the file however I don't understand how to set this up: |
Hi @MoskalykA, this the basic config file: //ddosify_config.json
{
"request_count": 20,
"load_type": "linear",
"duration": 5,
"proxy": "http://proxy_host.com:proxy_port",
"output": "stdout",
"steps": [
{
"id": 1,
"url": "https://test_site1.com/endpoint_1",
"protocol": "https",
"method": "POST",
"headers": {
"ContenType": "application/xml",
"header1": "header2"
},
"payload": "Body content 1",
"timeout": 3,
"auth": {
"username": "test_user",
"password": "12345"
}
}
]
} You will start ddosify with a ddosify -config config_examples/config.json Once the user selects the config file, the other options like target URL, load types, etc. must be disabled or disappear. If you have other questions, please let me know, thanks. |
Add config file support from Ddosify. Users should be able to import a config file on the Ddosify Docker extension. If a config file is imported, the other options like target URL, load types, etc. must be disabled.
The text was updated successfully, but these errors were encountered: