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

Separate sensitive data to a git submodule or an external database #2

Closed
oesteban opened this issue Apr 25, 2023 · 0 comments
Closed
Assignees
Labels
enhancement New feature or request

Comments

@oesteban
Copy link
Member

What would you like to see added in this software?

Sensitive information mustn't make it into the git history at any moment. Otherwise, when making the SOPs public then, it is necessary to go through the full history to remove those data (which is highly unsafe).

One option was not to recommend the publication of the git repo, only generate HTML with the information redacted. While this would serve the purpose of sharing the SOPs, there could be interesting information encoded in the git history itself, which would make the experiments described by the SOPs more reproducible (e.g., conversations and commit messages can be now used to understand things).

So I can see two options:

  1. have simple yaml/toml files on a private git repo that is added as a submodule
  2. have a mongo installed and store the data there

I would lean towards option 1.

Do you have any interest in helping implement the feature?

Yes

Additional information / screenshots

No response

@oesteban oesteban added the enhancement New feature or request label Apr 25, 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

3 participants