Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#35545 - {wiki} Track LocalSettings.php in repository

Attached to Project: Arch Linux
Opened by Dario Giovannetti (kynikos) - Wednesday, 29 May 2013, 16:10 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 11 July 2016, 12:25 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 13
Private No


I'm wondering if it's possible to remove LocalSettings.php from ArchWiki's .gitignore: this would make it much easier to submit patches for e.g. updating group permissions, changing default behaviours, etc.

The only problem would be hiding variables like database settings, which is probably why now the file is ignored, but I guess they could be moved to another file, which could in turn be required in LocalSettings.php
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 11 July 2016, 12:25 GMT
Reason for closing:  Implemented
Comment by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 21:49 GMT
As this git repo is used by other sites as well including LocalSettings does not seem practical.
Comment by Dario Giovannetti (kynikos) - Wednesday, 13 November 2013, 17:52 GMT
  • Field changed: Percent Complete (100% → 0%)
Sorry for reopening, but this would have been as practical as creating a / file with the public settings and requiring that in the untracked /LocalSettings.php file with the private variables.

The other websites using this repo could do the same, e.g. /

Other examples of custom files already present in the repo:
* /extensions/ArchInterWiki.sql
* /skins/archlinux/*
Comment by Sebastiaan Lokhorst (lonaowna) - Saturday, 12 July 2014, 19:43 GMT
I agree, the settings mentioned by Dario are valuable enough to track through the repository, as they are essential to restore current state of the wiki. It would be nice to have them publicly available, with the private database settings separated.