Currently, when tigase-server detect any problem with config.tdsl file it overwrites it with "correct" one and make the backup of the previous one. This is less than ideal for a couple of reasons:

1. configuration file should not be automatically edited by the application -- bad practice
2. it tends to replace configuration file with some parts commented out with the "correct" one while making backup, which makes it very inconvenient to restore previous version (with comments and more elaborate configuration).

The backup mechanism tends to generate a lot of exactly the same files still:

~/dev/tigase/devops/tigase-deployment/config/tigase-server/etc on  master [!?]
🕙 [16:17:29] ❯ diff config.tdsl.old config.tdsl.old.1

~/dev/tigase/devops/tigase-deployment/config/tigase-server/etc on  master [!?]
🕙 [16:17:42] ❯ diff config.tdsl.old config.tdsl.old.2

~/dev/tigase/devops/tigase-deployment/config/tigase-server/etc on  master [!?]
🕙 [16:17:45] ❯ diff config.tdsl.old config.tdsl.old.3

~/dev/tigase/devops/tigase-deployment/config/tigase-server/etc on  master [!?]
🕙 [16:17:46] ❯ diff config.tdsl.old config.tdsl.old.4

~/dev/tigase/devops/tigase-deployment/config/tigase-server/etc on  master [!?]

Proposal:

1. flip the mechnism: leave the config.tdsl file as is (it's loaded either way) and instead output correct version to: config.tdsl-new file
2. ideally check if there is no file like that and if it's not the same to avoid pointless multiplication