I'm fiddling with automating rebuilding my setup and one of the 
customizations I make is to disable the default enabled skin(s) and to only 
enable my custom skins.  This requires me to hand-edit weewx.conf which is 
contrary to the idea of full automation (ansible or the like).

I know we have wee_config to switch drivers and do rudimentary editing of 
weewx.conf, so I was wondering if it's reasonable to try to extend that to 
enable/disable skins and/or set their HTML_ROOT parameters etc.

Not asking anybody to do any coding, just wondering if it would be of any 
interest...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/8eef2433-51e8-48d3-923b-13df129c8a7dn%40googlegroups.com.

Reply via email to