Vince,Watch this space. We are writing a weewx / skin admin page to go with the successor of weewx-Weather34. I am sure that this could be adapted to be portable for the greater good of the WeeWX universe.IanSent from my iPhoneOn 23 Nov 2022, at 21:31, vince wrote:Mine is
Mine is https://github.com/vinceskahan/weewx-docker if anybody has
interest. Not too bad at 205MB with Belchertown installed and enabled :-)
Hardest thing is lots of extensions/skins are either mis(un)configured out
of the box or disabled. The configobj format of weewx.conf makes it
Vince/Tom:
Actually I built my own image. It essentially builds weewx via python
setup.py and I add a few popular extensions (mqtt, forecast, belchertown)
as a "batteries include" release.
My docker image performs all of it's logging to stdout, so you can review
the logs in your favorite
On Wednesday, November 23, 2022 at 4:21:07 AM UTC-8 t...@tom.org wrote:
> Phusion is a weird base image, but it did a nice job of supporting the
> logging requirements of weewx. I would love a collaborator to either
> optimize this one or base it on another base altogether. I think Doug is
>
Re the Docker image, Vince is right that it did not support anything but
what I was using, which is x86-64 (I run my instances as Kubetnetes pods).
Now it supports arm, arm64, and x86-64.
Phusion is a weird base image, but it did a nice job of supporting the
logging requirements of weewx. I
For my docker configuration for my weewx weatherstation, I add this
configuration right after the version = x.x.x line. Give it a couple of
empty lines to separate it out
###
[Logging]
version = 1
disable_existing_loggers = False
# Root
Thanks for the explanation. Doug+I are doing the same thing. Suppressing
LOOP via removing StdPrint and redirecting logging using the v4 logging to
console as you documented for the wiki in the spring. Difference is I'm
building up from base debian as a starting point.
[...tl;dr...]
Doug's
StdPrint is sending messages directly to stdout via print() statements ---
the logging facility is not involved at all. So, no, I would not expect
that to work.
Doug is using a log handler that sends log messages to "console," that is,
stdout. So, what you're looking at is a mixture of print()
Sorry for the late reply. Rebuilding/consolidating my docker setups and
had a question...
Removing StdPrint 'does' work for suppressing the LOOP messages in Docker,
but is there a way to get the same effect via a custom [Logging] stanza ?
I got very lost under the hood trying to follow how
Thanks Tom I appreciate it! Worked as expected :)
On Sunday, March 27, 2022 at 7:28:52 AM UTC-4 tke...@gmail.com wrote:
> Just remove "StdPrint" from the list of reporting services to be run. So,
> this
>
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> becomes this
>
>
Just remove "StdPrint" from the list of reporting services to be run. So,
this
report_services = weewx.engine.StdPrint, weewx.engine.StdReport
becomes this
report_services = weewx.engine.StdReport
On Sun, Mar 27, 2022 at 4:24 AM Doug Jenkins wrote:
> Good Morning:
>
> I am preparing a
Good Morning:
I am preparing a docker image for my new weatherstation. I am configuring
WeeWX the "docker way" where the log data in being written to the stdout
via logging handlers.
When I run WeeWX (both in a docker container and on a VM itself), I always
see the LOOP output written to
12 matches
Mail list logo
