You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing again with the crt.sh codebase and have a new database server up and running and started up the ct_monitor application, however (after reading the code even) I'm still a bit puzzle what all the configuration params are supposed to do.
# This indicates to me it's possible to use multiple connection however only 1 is ever used?
connopen = 16
connidle = 4
connlife = "10m"
# The interval looks clear and is a "pause" in monitoring when no work is available?
interval = "1s"
# These 3 are the most puzzling to me what exactly they control?
batch = 5000
concurrent = 256
chunk = 2048
# This controls the timeout of the HTTP connection to the logs?
httptimeout = "30s"
# This one actually is clear to me and is just the postgres connection info :)
conninfo = xxx
Hope you have some time to explain a bit what is what and / or provide what crt.sh is running.
Thanks for providing crt.sh and the code for it allowing others to have a similar setup!
The text was updated successfully, but these errors were encountered:
Hi Rob,
I've been playing again with the crt.sh codebase and have a new database server up and running and started up the
ct_monitor
application, however (after reading the code even) I'm still a bit puzzle what all the configuration params are supposed to do.Hope you have some time to explain a bit what is what and / or provide what crt.sh is running.
Thanks for providing crt.sh and the code for it allowing others to have a similar setup!
The text was updated successfully, but these errors were encountered: