we have published our LocalSettings.php and simply excluded the
"secrets" which are in a separated folder (and excluded with .gitignore)
see Line 44 for example:
You can include with such a constellation everything you need.
Am 20.01.2016 um 15:56 schrieb Ray Paseur:
Colleagues: I'm looking for some "best
practices" advice here.
I have three Wikis, Dev, Test, and Prod. Dev is the sandbox. Test is for
user-acceptance. Prod is the public face - exactly what you would expect.
For the most part, these Wikis share an identical code base on Git branch
"master." Development is done in branches that are pulled into master as user
acceptance is completed.
There are differences between the Wikis environments, and so I've got three
LocalSettings.php files. I can't just pull the Dev into Test or the Test into Prod
because of differences in the LocalSettings (database connections, error_reporting, etc).
Right now I'm doing a manual process outside of Git control. This makes me itch.
I would like to keep LocalSettings.php under Git version control with the rest of the
code, but that means three files with the same name.
Would I be on firm ground if I modified LocalSettings.php to automatically detect which
Wiki is in play and adjust its own settings? How do others handle issues like this?
MediaWiki-l mailing list
To unsubscribe, go to: