Page MenuHomePhabricator

Implement configuration database aka configuration management aka no shell excuse
Open, MediumPublic

Description

At brion's suggestion, a lot of site requests should not require the "shell" keyword. For example, logo change requests.

This bug tracks bugs that would help get reduce the number of bugs that require the "shell" keyword.


Version: 1.21.x
Severity: enhancement
URL: http://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database

Details

Reference
bz26992

Related Objects

StatusSubtypeAssignedTask
ResolvedNone
DeclinedTTO
OpenNone
ResolvedNone
DeclinedNone
OpenNone
OpenNone
DeclinedNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
ResolvedxSavitar
OpenNone
ResolvedTgr
ResolvedAnomie
ResolvedJoe
ResolvedJoe
Resolvedhashar
Resolvedbd808
ResolvedAnomie
ResolvedKrinkle
ResolvedNone
ResolvedJanZerebecki
ResolvedKrinkle
ResolvedTgr
OpenNone
ResolvedTchanders
ResolvedNone
ResolvedFlorian
ResolvedFlorian
OpenNone
OpenNone
OpenNone

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:15 PM
bzimport set Reference to bz26992.
bzimport added a subscriber: Unknown Object (MLST).

From talking to JeLuF, he says he sees these requests most of

  • Change logo
  • Change namespace
  • Add groups
  • Enable extensions and install initial config
  • Change config settings for extensions that people forgot to put into the initial config

I'll see if I can't come up with separate, reasonable requests for each of these.

(In reply to comment #1)

http://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database

This. We don't need 5 separate solutions to solve this. We need one configuration solution done right.

I would still like it, but I haven't had time to spend any time on
it. I think Chad's work is probably the best way to go, but I don't
think he has much time to work on it.

I'll be tackling this after the git migration, it's on the roadmap for May-ish.

If the configuration were in git as the site itself, it could be handled with gerrit.

(In reply to comment #7)

If the configuration were in git as the site itself, it could be handled with
gerrit.

That could also be an option, but I'd still like to see us overhaul how we handle config management in MW.

  • Bug 29863 has been marked as a duplicate of this bug. ***
  • Bug 16595 has been marked as a duplicate of this bug. ***

Changing summary: I got sick of not finding this bug.

(In reply to comment #6)

I'll be tackling this after the git migration, it's on the roadmap for May-ish.

What's the status?

(In reply to comment #12)

(In reply to comment #6)

I'll be tackling this after the git migration, it's on the roadmap for May-ish.

What's the status?

Right now I'm planning to get underway sometime in August. Git/Gerrit has taken much more time than I ever anticipated.

pushing to future since release is imminent.

(In reply to comment #13)

Right now I'm planning to get underway sometime in August. Git/Gerrit has taken
much more time than I ever anticipated.

What's the status?

I assume that Chad is too busy with other stuff currently, but it's true that "It has the power to resolve dozens (maybe hundreds?) of bugs." (as MZMcBride said on IRC), and we do have a huge backlog here.

  • Bug 36370 has been marked as a duplicate of this bug. ***

Setting as Normal just to reflect the reality. Feel free to prioritizy as High if/when work starts.

PS: found during https://www.mediawiki.org/wiki/Bug_management/Triage/20130307

  • Bug 36857 has been marked as a duplicate of this bug. ***
  • Bug 36370 has been marked as a duplicate of this bug. ***

This will hopefully be discussed at the Architecture Summit: [[mw:Architecture Summit 2014/Configuration]].

The first step of this was merged to core: https://gerrit.wikimedia.org/r/#/c/109266/

The idea is that by using a Config class rather than directly calling globals, it will be easier to later swap the backend to a database/HipHop/whatever .

For this to fully work, everything eventually has to use that Config class.

(In reply to comment #22)

For this to fully work, everything eventually has to use that Config class.

The API already has a migration patchset :D

It is time to promote Wikimedia-Hackathon-2015 activities in the program (training sessions and meetings) and main wiki page (hacking projects and other ongoing activities). Follow the instructions, please. If you have questions, about this message, ask here.

Did someone work on this project during Wikimedia-Hackathon-2015? If so, please update the task with the results. If not, please remove the label.

Phabricator_maintenance renamed this task from Implement configuration database aka configuration management aka no shell excuse (tracking) to Implement configuration database aka configuration management aka no shell excuse.Aug 13 2016, 10:10 PM