@Trizek-WMF Since you are the one who prepares a set of configuration variables for me to use when deploying, can you have a look at this one, please?

Could we use extension.json for using the defaults? Using Wikidata seems like it might get complicated quickly, and would be more difficult to set up for local development and testing.

For example, we could do something like:

"WelcomeSurveyEnabled": {
	"description": "Global ON/OFF switch for the Welcome survey feature.",
	"value": true,
	"allowOnWikiOverride": true,
},

I'll have a look at it next week. Meanwhile, if it can help, you can have a look at the existing documentation that includes the default values.

In T275789#6864141, @kostajh wrote:

Could we use extension.json for using the defaults? Using Wikidata seems like it might get complicated quickly, and would be more difficult to set up for local development and testing.

If I understand it right, the defaults are different per each wiki. For instance, we set manual of style to whatever is in Q4994848, etc. I'm not sure how to do it with extension.json.

In addition to per wiki defaults, there will be also global defaults, set via extension.json.

Does this make sense Kosta?

In T275789#6864374, @Urbanecm_WMF wrote:

In T275789#6864141, @kostajh wrote:

Could we use extension.json for using the defaults? Using Wikidata seems like it might get complicated quickly, and would be more difficult to set up for local development and testing.

If I understand it right, the defaults are different per each wiki. For instance, we set manual of style to whatever is in Q4994848, etc. I'm not sure how to do it with extension.json.

In addition to per wiki defaults, there will be also global defaults, set via extension.json.

Does this make sense Kosta?

Ah, right. Yes, that makes sense. Thanks!