On Nov 8, 2022, at 5:48 AM, Doug Jenkins <[email protected]> wrote: > > 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).
If by user you mean interactive user where shell access and remote login is possible,I disagree with the idea of the config files being in an interactive-access user’s home directory (unless the user is “weewx” - an account dedicated for running weewx) for the following reasons: 1) Weewx is typically run on systems which do not have multiple users. So the benefit of per interactive user is what? 2) to me, anything that is run on system boot up, started by a system init function (sysv) or systemd or whatever and stays running the entire time the system is running is a system-level application which should run from a safeguarded and isolated system account - not a user account with interactive login capability. 3) storing weewx application data ( even configuration data) remotely on the file system from the Weewx installation area would be a hassle to me. I like that my installation of Weewx is portable - fully contained in the home/Weewx tree and the only external bits are the system startup script and the pointer from my web home page to /home/Weewx/public_data. Again, if by this you mean Weewx config data is stored in home/Weewx, I’m entirely fine with it. -- 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/5FC5A379-CA06-4B10-9F8B-8953A70CE2D2%40gmail.com.
