First off, Thanks Matt and Tom for the great wiki article! It is a breath of fresh air to see the level of thought and purpose put into this piece of software.
I read the wiki and I do like the idea of the CTL pattern. This will be a good start to get the "code/data" separation going. I do think it should be considered to install the configuration files in the user's home directory as that would be a secure way to manage the tool and would be a lot easier for new users to perform backups (eg backup weewx-data/ directory). Also a big benefit of the CTL tool/class will be for extension writers. They can invoke the tool to add/edit config items directly, kind of in the same way as the ExtensionInstaller Class works now. I have been noodling on a solution to help users who are not as strong technically get WeeWX up and to manage it. I have been designing a WeeWX Admin interface as a companion product to help users manage their WeeWX instance as a software appliance. I will publish a separate thread on this to get feedback from the dev community later today. Just a FYI , I added the link to the article to this thread for others to review and opine : https://github.com/weewx/weewx/wiki/installer-options Thanks, Doug Jenkins largoweather.com On Tue, Nov 8, 2022 at 7:37 AM Greg Troxel <[email protected]> wrote: > > matthew wall <[email protected]> writes: > > > where the conf lives is not yet clear. for apt/yum it is clear - they > live > > in /etc/weewx. for a python install, we are considering ~/weewx of the > > user who created the station instance (not necessarily the same as the > user > > who installed weewx). from a support point of view, it would be nice if > > the conf file (and skins and database) were always in the same place. > i'm > > not sure if that is possible, since the developer use case wants these > in a > > single directory in the user's home directory space, whereas that is > > non-standard for an apt/yum install. > > That's a really interesting point, between weewx as a system daemon with > config in the standard place, and alternate config. > > I would suggest that by default the standard config is read and there is > a "-C /path/to/the/weewx.conf/I/want/to/use" and also have that file be > able to set paths to database, etc. > > Also for development one could just do the normal install with > --prefix=$HOME/weewx-devel or whatever, I think. > > -- > 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/rmiv8npk4gg.fsf%40s1.lexort.com > . > -- 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/CACC0i0zSzh30CCM6V-yH6fn0stfxz4dupE1nnXinuDT2psH67w%40mail.gmail.com.
