Pat and I were discussing his Belchertown skin via email and I mentioned that I do the 'salt to taste' by editing skin.conf for the skin rather than editing the toplevel weewx.conf file. He had a cow, man :-)
I know it's largely equivalent at runtime, but I was wondering if best practice is to edit weewx.conf or skin.conf to 'tune' a particular skin. Why I use skin.conf: - it localizes all changes 'in' the skin - you can change stuff there without resetting weewx itself, so dev/test/fix/test-again cycles are quicker - I build my stuff with scripts, so for me I'd install/upgrade a vanilla skin and supersede skin.conf with a Github-stashed file as part of installing/upgrading a skin, so I don't care if the vanilla skin overwrites previous changes. I just overwrite the skin.conf with a configuration-controlled file. Why Pat likes skin.conf: - it makes skin updates simpler, just overwrite the installed skin tree completely, since weewx.conf edits persists of course Is there a preferred place to do these skin configuration type edits ? Does (or can) the extension installer have some concept of keeping the old skin.conf file ? For those who build RPMs, I'm thinking along the lines of how you can define a file as being a 'config' file and set whether it's overwritten, kept, set to not be replaced/overwritten, etc. It's been enough years since I ever looked at this, that I haven't keep track of any changes that might have happened since the wee_extension magic was cooked up, so I thought I'd ask....
