[Dancer-users] "sensitive" config data in SCM

[Mr. Puneet Kishor]

Not a Dancer question per se, but I am sure a few of you have encountered this, and it is a "best practice" issue I am encountering for my Dancer apps, so --

I have hard at work learning Git, striving to put all my work in a Git repo (including Github, where appropriate). Yesterday I realized that I would be committing my database and other passwords to the repo as well (I am using the most excellent Dancer::Plugin::Database). A little bit of searching brought me to the conclusion that I had to implement some kind of "smudge" and "clean" filters using .gitattributes -- so when I commit my work to the repo, the sensitive info would get replaced by **** (or other placeholders), and when I would checkout the work, the placeholders would get replaced by the real info.

Before I waste too much time learning and implementing these smudge and clean filters, it would behoove me to ask if one of you already has those in place, and if you would kindly share them with me and the community... appropriately via Github.

Many thanks in advance,

Puneet.