Topic on Talk:Developer Satisfaction Survey/2019

This has probably been debated in the past, but I'm curious what people think about containing the dev environment configuration for an extension within the extension repository. Currently, if I add new settings to an extension, I have to go to the vagrant repo and update one or more files to set the desired development settings. It's easy to forget to do this, and easy for settings to become out of date.

Perhaps in the 'config' key in extension.json, in addition, to 'value' there could also be 'development_default_value'? Some extensions have more complicated setup tasks, but even there IMO it would be better to have the ability to maintain any development configuration scripts in the extension rather than in an external location.

+1 this sounds great. I can imagine that it would be challenging to provide development config that will be helpful outside of the vagrant context, for example when one extension requires specific ports or database config to interact with another extension. Maybe a variation on this proposal would be to move the mw:Extension:Foo configuration documentation into a "Foo.conf.sample" file, which is purely documentation but friendly to copy-pasting.

This is a good idea and I think we should definitely do something to address this need.

Usually this is handled by an environment config file which overrides the defaults. Then you can have dev, test and prod versions of this file with appropriate settings for each environment.