🔧Improve env with `make bootstrap`

[AntoLC]

Bug / Improvement Report

Prob:

• Our users are not specially aware about our env.d system
• A user installs the project for the first time
• He makes make bootstrap
• make bootstrap will copy common.dist to common
• A few weeks later, the same user comes back to the project
• Some keys in common.dist have changed
• The user makes make bootstrap
• ⚠ The new keys are not added or updated in common
• The app fails

Prob location

cp -n copy only if the file does not exist already

docs/Makefile

Lines 232 to 233 in 5be2bc7

	env.d/development/common:
	cp -n env.d/development/common.dist env.d/development/common

Solutions ?

• Merge the files, if the key exist don't overload, and add just the new key ?
• Or save the old common files by renaming it (common-save-2701250950), then redo the make env.d/development/common ?

This problem applies for others env/files as well (postgresql and kc_postgresql).

[virgile-dev]

@lunika did you improve this ?

[lunika]

No, the work I made about the bootstrap is not related to this issue.

IMO this is more related to a lack of documentation about how to upgrade the application from version X to version Y. The changelog should reflect the addition of a new settings or we should create a UPGRADE.md file containing this kind of information. This information will be helpful for the community to know what they have to do to migrate to a new version.

[lunika]

Also having a documentation containing all the application settings explaining their purpose, default value, etc is also a good idea

[virgile-dev]

@AntoLC can we update this issue with @lunika suggestions ?