On Friday, December 10, 2021 at 3:05:15 PM UTC-5 [email protected] wrote:
> 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. > this seems like a reasonable set of options to add to wee_config. perhaps something like this: wee_config --enable-skin SKINNAME wee_config --disable-skin SKINNAME if the skin has been installed (i.e., there is a block in the weewx config file with the name SKINNAME), it enables the skin in that config file. to do HTML_ROOT or other parameters that can be used with all skins we might need something more generic... notice that this would not care about the actual weewx installation (e.g., contents of the skin directory) - it would only have to look at the specified config file. (btw, wee_config should have the option '--config filename' so you can use this with any weewx config file, not just weewx.conf) this is somewhat analogous to apache's a2x commands for enabling and disabling mods and confs. that way ansible or salt or whatever does not have to worry about how a weewx config file is parsed/formatted. m -- 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/23ae3733-2dc9-414c-bcbf-bc8cad2a002en%40googlegroups.com.
