We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we don’t have documented how to set up and run go-ftw for rule developers.
Create a documentation page under development and explain:
ftw
.ftw.yaml
Btw, my .ftw.yaml (if it's not already doc'd somewhere) is:
--- logfile: 'tests/logs/modsec2-apache/error.log' logtype: name: 'apache' timeregex: '\[([A-Z][a-z]{2} [A-z][a-z]{2} \d{1,2} \d{1,2}\:\d{1,2}\:\d{1,2}\.\d+? \d{4})\]' timeformat: 'ddd MMM DD HH:mm:ss.S YYYY'
We should have Nginx/Coraza too, maybe in the future and do it in steps.
Explain it manually to people 30 times. 😉
N/A
The text was updated successfully, but these errors were encountered:
Can we replace the legacy Python ftw instructions? That will mean no duplication. (https://coreruleset.org/docs/development/testing/)
Sorry, something went wrong.
That seems quite sensible to me!
No branches or pull requests
Motivation
Currently we don’t have documented how to set up and run go-ftw for rule developers.
Proposed solution
Create a documentation page under development and explain:
ftw
binary one time with right click and Open.ftw.yaml
Btw, my
.ftw.yaml
(if it's not already doc'd somewhere) is:We should have Nginx/Coraza too, maybe in the future and do it in steps.
Alternatives
Explain it manually to people 30 times. 😉
Additional context
N/A
The text was updated successfully, but these errors were encountered: