Tom, Matthew, Gary and the team. This is outstanding. I am in full 
admiration of you guys for what you do, the support you provide (believe 
you me I know how difficult that can be), the many hundreds of hours of 
your time patiently and freely given - just everything. The pip install 
method is such a revelation, once setup it is a dream to use - yes it is 
wonderful. The most important thing for me however is the sense of 
community you bring to users from all over the world. 
Congratulations
Ian

On Monday, January 15, 2024 at 9:24:55 PM UTC matthew wall wrote:

> On Monday, January 15, 2024 at 3:52:31 PM UTC-5 [email protected] wrote:
>
> Curious what the recommended install method is, aside from personal 
> preference.  Been running weewx on a Pi4 for a few years now and have been 
> waiting for official release to migrate it over to bookworm and a fresh 
> install, as there's a feature or fix or two I think I can take advantage 
> of.  Since it won't technically be an upgrade (I'll attempt to migrate data 
> over after as I'm MySQL based), I can use apt or pip.
>
> Any advantages to either?  This will be a dedicated pi just for weewx, if 
> that matters.
>
>
> i tend to use the deb or rpm install for the systems where i use weewx as 
> an appliance, for example, data collection on a construction site, or 
> monitoring temperatures and weather conditions at facilities.  in this use 
> case, i just want to get the sensors out there so i can collect the data; i 
> want to spent very little time installing, let alone tweaking a dashboard 
> or driver parameters.  having local storage and 'Seasons' skin is helpful 
> for basic diagnostics and redundancy (e.g., when the network dies), but i 
> typically send the data to an MQTT broker and/or influx server for 
> aggregation and analysis.
>
> i use the 'git' method when i am working on weewx code or a driver or 
> skin, because there is no install - i make the changes then immediately see 
> the results.  the 'git' method works well for this, but it requires too 
> much fiddling for production data collection.
>
> if you want to insulate yourself from the whims of the operating system, 
> the pip approach with virtual environment is wonderful.  you can run a pip 
> install on *anything*, whether it is an old arm machine that no longer gets 
> updates, a router, or a pi that you just want to set and forget.  you just 
> need python3.6 or later.  compared to a dep/rpm install, the pip approach 
> requires more steps to set up and integrate with your system (the init 
> stuff, the udev rules), but the setup-daemon.sh script in v5 does that for 
> you now, or at least shows you how to do it (if you prefer to do it all 
> yourself).
>
> if you are running multiple drivers on a single computer, deb/rpm or pip 
> is really easy now.  on linux systems that use systemd there is now a unit 
> template, and on linux systems that use sysv the 'weewx-multi' script is 
> now the default rc script.  so running multiple instances is no longer a 
> reason to choose a python install over a deb/rpm install.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" 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-user/c200840c-ddf0-4ac7-a928-c08db7f75c9dn%40googlegroups.com.

Reply via email to