We have a project with some sensitive data. We want the main project to be git* open/public, but we want the data to be somewhere secure and private, but ideally still connected to the first repo for those with permissions. I would like them to be able to just "git pull" or clone and get the sensitive data in the right location. Is there a git convention for this scenario, or should I just make a second, private repo and tell them to manually pull it into the right locations?
@souldessin does it work as far as data privacy?
@worldsendless
The ones I've setup rely on out of band credentials in a production yaml and a dev yaml and db that are part of the repo. The production data is never uploaded.
Yeah, we have the different dev profiles. Probably my desire for prod data privately in dev is my real problem. I have thought of having dev environments as close as possible to the prod one, and may have let that thought go too far
@worldsendless
There is a method for making the configs to be used in production and then in development.