es werden keine Werte für
there are no values for
Server-Laufzeit$station.os_uptime
WeeWX-Laufzeit $station.uptime
WeeWX-Version 4.10.0a1
SkinSeasons 4.10.1
nicht angezeigt
in weewx Version: 4.9.0
WeeWX-Laufzeit: 5 Tage, 22 Stunden, 21 Minuten
Server-Laufze
The idea of a wee_ctl utility is interesting, but a tough one perhaps given
how very flexible weewx is and how creative folks have been over the years
leveraging that flexibility.
I'll attach an obfuscated weewx.conf from my system. Any new solution
would have to be able to generate something
we have a wiki page devoted to installation options. it is a bit haphazard
right now (especially the 'ctl' pattern), but it does capture some of the
issues:
https://github.com/weewx/weewx/wiki/installer-options
please refrain from modifying the wiki page - tom and i are trying to
curate it in
Joel Bion writes:
> One other question: is it possible to ask the user, instead of running
> setup.py, to run a script located in the weewx 'top level directory' that
> does the following: (a) uses the new form Python install/upgrade (b) then
> runs separate code (even if it's in python) to upgr
One other question: is it possible to ask the user, instead of running
setup.py, to run a script located in the weewx 'top level directory' that
does the following: (a) uses the new form Python install/upgrade (b) then
runs separate code (even if it's in python) to upgrade the .ini file, put
things
Perhaps review the original setup.py vintage weewx design principles and
see if any have changed due to the distutils deprecation ?
- be pure python for everything
- install everything to one tree
- except os-required things (startup file and custom syslog configs)
And of cours
On Mon, Nov 7, 2022 at 2:20 PM Chris Richmond wrote:
>
> Is there a concise problem statement related to all this? It's funny that
> over the years (decades) I think much better working from
> a problem statement.
>
Good comments. As for the config problem statement, I don't know. You'd
have to
Maybe I've missed the whole point of these proposed changes, but I'll offer
my experience on the offhand it might help.
For a *very* long time, when I was working, we had two very large sets of
tools, the first in Perl, then a complete re-write
in Python. In both cases, all the configs (a LOT of
