2 ms·
Nobody mentioned the fact that _you don't put secrets in a versioning system_. .gitignore the configuration files and have example files available, or use confi
by riquito 12y ago
Nobody mentioned the fact that _you don't put secrets in a versioning system_. .gitignore the configuration files and have example files available, or use configuration files that can import the missing parts (the secrets) from an ignored file.
Another way is to put the secrets in environment variables outside the project.
In any way, if they're missing provide a meaningful message to the developer.
I do understand that you must keep some of these secrets available somewhere: just don't version them.
- ansible 12y agoI can understand the desire to version control your secrets. The bad idea was not to maintain the source in a separate repo that could easily be released. If you want to keep the checkout process simple for your developers, maybe use git subtree for the overall project.