-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update without losing skin.conf (update-script) #58
Comments
Well, yes this would be a simple task to write a basic update script, but as you noted, this only works if there are no updates in the skin.conf. Otherwise, these values would also need to be updated (which could be tricky to do in a shell script). I wonder if there is any chance to make such updates like 'automatically merge the user skin.conf with an updated skin.conf' working with weewx API. I will do some research and also post a Edit: Note to myself: Perhaps it would be useful for users if I would post the changes (if any) that were made to the skin.conf in every release in the release notes. |
Sorry I did not get this ready before the new 2.2.0 release, but I added a new section to the release notes 'Changes made to skin.conf since 2.1.0', which should make the manual update easier. |
There is another way to do to avoid that skin.conf settings are overwritten by an update : copy to weewx.conf the personalized item of the skin.conf. [[WdcReport]] you can do the same for any other settings. By adding personalized Display options, weewx.conf will be : [[WdcReport]] As explained here: https://www.weewx.com/docs/customizing.htm#Processing_order , skin configuration items in weewx.conf will override corresponding items in the skin.conf :
|
@Jterrettaz Well, I did not know about this, thank you very much for pointing this out! I will update the wiki to contain this information. |
I added a section about this in the wiki https://github.com/Daveiano/weewx-wdc/wiki/Configuration#persisting-changes-to-the-skinconf-between-updates and also updated the readme. @Jterrettaz Thanks again for pointing this out! |
if I update the skin, I have to uninstall it and then reinstall it. So my question is, can you build an update script that saves the skin.conf, then installs the update and restores the skin.conf? But that would only work if you didn't change anything in the skin.conf in the course of an update. Otherwise the skin.conf would not be suitable for the new version.
If that were possible, the weather forecast and the radar images would not have to be reimplemented with every update.
The text was updated successfully, but these errors were encountered: