Simplify production DATABASES setting to extend base definition

[adinhodovic]

Description

Remove production db settings being instantiated twice when using docker.

Checklist:

• I've made sure that tests are updated accordingly (especially if adding or updating a template option)
• I've updated the documentation or confirm that my change doesn't require any updates

Rationale

I believe each env.db() resets the dict. Keep shared settings in base.py. Otherwise we have to redefine every db parameter, such as atomic requests.

[foarsitter]

This indeed looks like a duplicated definition, but why is there an exception needed for a non docker environment? The initialisation is the same right?

[browniebroke]

This indeed looks like a duplicated definition, but why is there an exception needed for a non docker environment? The initialisation is the same right?

Thanks for bumping this discussion and raising this point, I have the same question. It feels like we could remove this altogether?

[adinhodovic]

This indeed looks like a duplicated definition, but why is there an exception needed for a non docker environment? The initialisation is the same right?

Thanks for bumping this discussion and raising this point, I have the same question. It feels like we could remove this altogether?

Hmm, makes sense now when I took a second look can remove it altogether. Updated.