fix(ignore): removes cached data/configuration.yaml

[mateja176]

Firest reference .gitignore:

# Ignore config
data/*.yaml
!data/configuration.example.yaml

Second reference Linux configuration docs.

[Koenkk]

I really would like to get rid of this file but it will break existing setups (for those having checkout before 70a72dd)

[mateja176]

I really would like to get rid of this file but it will break existing setups (for those having checkout before 70a72dd

Let’s imagine that John Doe cloned the repo before ‘70a72dd’. If John pulls the latest commit, following this PR, his local ‘configuration.yaml’ will be preserved. What’s the scenario you’re wary about?

[Koenkk]

He will get a merge conflict I believe

[mateja176]

He will get a merge conflict I believe

I've tested a couple of scenarios:

• If data/configuration.yaml hasn't been updated, it will get deleted after pulling this commit. Though no data is lost, becuase it's straightforward to recreate it by running cp data/configuration.example.yaml data/configuration.yaml or copy-pasting its contents from the git history.
• If data/configuration.yaml has been updated, it's a prerequisite to backup the changes and discard them from the working directory, in which case it's trivial to recreate the file from the backup. Alternatively, if the changes are stashed before pulling this commit, after poping the stash and choosing the option Keep their version, the file will be added to the working directory in conjunction to being ignored by git.

[Koenkk]

can you integrate these changes in the update.sh script? I know not all users use this and I still expect a lot of issues to be reported due to this change but at least we tried 😀

[stefanrenne]

@Koenkk to get more awareness for the update.sh script, maybe its an idea to update this page ;) https://www.zigbee2mqtt.io/guide/installation/01_linux.html#for-later-update-zigbee2mqtt-to-the-latest-version

[Koenkk]

@stefanrenne done!