On Wed, Feb 27, 2013 at 9:13 PM, Daniel Friesen
index.php, api.php, etc... provide entrypoints into the configured wiki.
mw-config/ installs and upgrades the wiki. With much of itself
disconnected from core code that requires a configured wiki. And after
installation it can even be eliminated completely without issue.
I think this clarifies the issue for me. Correct me if I'm wrong, but
basically the entry points are for continued, repeated use, for indeed
*accessing* wiki resources (hence I suggest the normalization of the name
of these scripts to "access points" everywhere in the docs, because
is a little more generic), while mw-config/index.php is a one-off script
that has no use once the wiki installation is done. I'll update the docs in
accordingly, to make this clear.
I wouldn't even include mw-config in entrypoint modifications that would
be applied to other entrypoint code.
You mean like this one <https://gerrit.wikimedia.org/r/#/c/49208/>? I can
understand, in the sense that it gives people the wrong idea regarding its
relationship with the other access points, but if the documentation is
clear, I see no reason not to have mw-config/index.php benefit from changes
when the touched code is the part common to all *entry* points (in the
strict meaning of files that can be used to enter the wiki from a web
That said, and considering what Platonides mentioned:
It was originally named "config". It came from the link that sent you
there: "You need to configure your wiki
first". Then someone had
problems with other program that was installed sitewide on his host
appropiating the /config/ folder, so it was renamed to mw-config.
...I would suggest the mw-config directory to be renamed to something that
more clearly identifies its purpose. I'm thinking "first-run" or something
to that effect. I'll submit a patchset proposing this.