Configuration inheritance

[sayanarijit]

With the current configuration we are extending development.ini into production.ini and test.ini.

I think a better approach would be to use production.ini as the master configuration file and inherit both development.ini and test.ini from it. With this model, we can add additional configuration for development like the [pshell] directive which is not required in production. Same for testing.

This is also the way Python's dependency management works. pip install -e '.[develop]' or pipenv install --devinstalls all the production requirements and then installs development requirements as additional dependencies.

[zupo]

Completely agree. I was a blinders-wearing-horse, copying .ini files from our internal projects when I was creating this repo and didn't stop to think which way of inheritance is better. Thanks for pointing it out!

[sayanarijit]

We are now inheriting production.ini > development.ini > test.ini.

However, I think the inheritance should go like: production.ini > test.ini > development.ini.

Reason: Let's take production.ini as the master configuration to run the app.
Add some assertion to it, we get run + assert = test.
And with some debugging and coding, we get test + debug + code = develop.

e.g. https://github.com/niteoweb/pyramid-realworld-example-app/blob/master/shell.nix#L23-L26

[zupo]

Yep, I agree.