Skip to main content
6 events
when toggle format what by license comment
Jun 24, 2020 at 20:16 comment added user3625087 I feel like a second repository is good solution by splitting only sensitive information like password, project id, etc. into its own repo and leaving all other configuration data within the project's repo. That way, most of the config data that might change will stay in the project's repo to stay in sync with its source history, while data that rarely/never changes but is highly sensitive can live in a different repo.
Mar 7, 2018 at 21:54 comment added Seldom 'Where's Monica' Needy @Rogach They seem to attract a lot of hate, but git submodules would handle this just fine, I think – if the main one were set up right, and the restricted-access repo could just live inside it.
May 13, 2015 at 11:05 comment added Wolf A second store makes sense. There maybe other kinds of data, also confidential, that may be stored along with the configuration (for instance production data that is under analysis to fix problems of customers).
May 13, 2015 at 9:36 comment added kiwiron @Rogach I take your point. There are valid reasons to keep some configuration with the code, but as you say in your question, sensitive stuff needs to go elsewhere. So two repositories seems unavoidable. Also, I did not mention that app servers often help here. Data sources and JNDI variables can be set up by the administrator and will not be public.
May 13, 2015 at 9:23 comment added Rogach Having two separate repositories for one project seems like not a good idea - you can't do clean rollbacks or work with branches, because then you'll need to manipulate two repositories simultaneously (e.g. other branch requires some new config option, and when you switch to that new branch without also switching in config repository, things break in strange ways).
May 13, 2015 at 9:16 history answered kiwiron CC BY-SA 3.0