Last modified: 2014-07-10 19:25:17 UTC
From https://wikitech.wikimedia.org/wiki/Incident_documentation/20140328-DB-Queries#Actionables
14:53 < Reedy> Needs backup/remote repo (and backup of that)
Maybe put it the private ops repo we have for puppet configs?
(In reply to Krinkle from comment #2) > Maybe put it the private ops repo we have for puppet configs? Then no one who can deploy, who may need to change PrivateSettings (most likely, adding one), will be able to do so. Presumably that then also depends on puppet ensuring it's in place on tin, to then be synced out. Unless it goes somewhere else on the apache (et al) file systems, and we include/symlink it from there... I've created a private repo in /a/common/private, but it needs a remote to push somewhere (so it can be backed up), but obviously not gerrit. That's an aside. Not synced to production AdminSettings.php merged into PrivateSettings.php in the 2nd commit to the repo. private added to .gitignore in https://gerrit.wikimedia.org/r/145403 PrivateSettings.php and AdminSettings.php removed from .gitignore, and replaced with symlinks to ../private/PrivateSettings.php in https://gerrit.wikimedia.org/r/145404 Need to do something similar on beta for testing (and so it doesn't break it)
