In order to make make the provisioning and logging configuration easier, we should strongly consider splitting the log package into 2 distinct components:
log-server: receives, processes and writes received logs to disk
log-forwarder: sends logs to sd-log
It seems like, as a compromise, we could address this is packaging only, shipping only the configuration-specific changes required for sending or receiving logs, while using the same securedrop-log tarball
In order to make make the provisioning and logging configuration easier, we should strongly consider splitting the log package into 2 distinct components:
It seems like, as a compromise, we could address this is packaging only, shipping only the configuration-specific changes required for sending or receiving logs, while using the same securedrop-log tarball