config.yaml created prior to latest upgrade is retained with the previous property names

[freemansoft]

You can end up with an old incomplete config.yaml across releases. This is a common problem. Don't know if it should be fixed or just documented.

Steps

1. Run the project sometime in the past
2. A config.yaml will have been created
3. stop the environment
4. Get latest
5. Run the project
6. Notice that the old config.yaml created by copy was not replaced makes sense

Is this in release notes or something?

Workaround

1. Delete the config.yaml if you haven't made any changes to it (I did this in VS Code remote )
2. Delete config.yaml again to make it really die (I did this in VS Code remote)
3. Stop the project
4. Restart the project

Possible initial remedy

Add a comment at the top of the sample file saying

This was copied from config_sample.yaml and may need to be updated after upgrading the nim-anywhere project

Supporting docs

This is why I was confused about when I only saw one section in a in the config.yaml in the GUI in a previous problem report