Do you support 2 step authentication?

Like many projects, we deploy to many environments, QA, UA, Developer trunks, etc..

What is the best way to store sensitive configuration parameters in SVN? Or, should you not and just maintain a smaller unversioned file with credentials in it on the server?

Mainly, we do not want to expose production credentials to every developer.

2 ANSWERS

16th February 2017 at 9:57 am David Jackson

I’d rather provide configuration examples than real config files. In my project there is setup.default.php file in root directory that every user need to copy as setup.php and amend to match local environment. Additionally, to prevent checking in back customised setup files there is a rule for it in .svnignore.

$ echo 'setup.php' > .svnignore
$ svn propset svn:ignore -F .svnignore .

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.