Skip to content
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

[securedrop-log] Consider splitting securedrop-log into 2 distinct packages #1721

Open
emkll opened this issue Feb 7, 2020 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@emkll
Copy link
Contributor

emkll commented Feb 7, 2020

In order to make make the provisioning and logging configuration easier, we should strongly consider splitting the log package into 2 distinct components:

  1. log-server: receives, processes and writes received logs to disk
  2. 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

@kushaldas
Copy link
Contributor

I would suggest to split the source into two different projects, so that it becomes much easier to do the packaging.

@zenmonkeykstop zenmonkeykstop changed the title Consider splitting securedrop-log into 2 distinct packages [securedrop-log] Consider splitting securedrop-log into 2 distinct packages Dec 13, 2023
@zenmonkeykstop zenmonkeykstop transferred this issue from freedomofpress/securedrop-log Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants