Excellent write up! I'm am passingly familar with this configuration, just not with docker. Looks great.
On Tuesday, May 26, 2026 at 4:34:08 PM UTC-4 WeatheredScientist wrote: > Hi Vince (same user, new email). Thank you for doing that. I took that and > used it as inspiration (again, lots of LLM, shameful I know, but what I can > do is guide a somewhat amnesiac and hyperknowledgable employee) and managed > to shrink my docker image by about the same amount you did, but using > ubuntu 26 and python 3.14. > > I've been busy adding little features and what not. With a goal of > explaining it all and making it easy, I've put together a readme and create > a new release (2.0) of my take on weewx-rtldavis. This is now the > main/latest release now, though I am still tweaking a few things (e.g., > working on monitoring dropped packets for a sense of RF rx quality, helpful > for adjusting gain). > > > https://github.com/WeatheredScientist/weewx-rtldavis/releases/tag/v2.0-ubuntu26 > > I'd be very interested in everyone's feedback on the features, the > explanations, the whole lot. Trying to make this the best it can be, albeit > within my limits. > > Apologies if I've overstepped in using your repo as inspiration. > > On Friday, May 22, 2026 at 4:38:16 PM UTC-4 Vince Skahan wrote: > >> Just one last update - I took your starting point and tweaked it a bit to >> do a multistage build to drop the size by 75% and added a >> docker-compose.yml file to bring everything up and save persistent storage >> under /mnt/weertlsdr/{archive,log,public_html} for non-NAS users. Works >> fine here for me on a current raspios pi4 under docker. >> >> https://github.com/weewx-contrib/weewx-rtldavis/tree/main/docker if you >> wanted to take a look. >> >> Thanks again for posting the good starting point. >> >> On Thursday, May 21, 2026 at 8:40:35 AM UTC-7 WeatheredScientist wrote: >> >>> It is meant to be a starting point. I'm bandwidth limited at this point >>> in life, so can't just pick up the skills necessary to do it right. AI was >>> not just a convenience but a necessity, despite my many reservations about >>> it. This was an acceptable use case in my book. >>> >>> On Thursday, May 21, 2026 at 11:06:34 AM UTC-4 Vince Skahan wrote: >>> >>>> Interesting but risky. Having done this kind of stuff for so long my >>>> continued fear is minimally functional unsupportable garbage. It gave you >>>> a >>>> working solution ‘as a starting point’ which is fine but ‘shipping the >>>> prototype’ rarely ends well. >>>> >>>> And 100% of what it told you was fiction. You”ll not learn best >>>> practices not spot security or privacy holes, nor learn what good even >>>> looks like. If that works for you, cool. You scratched your itch, and >>>> thanks for the github repo which is always appreciated, >>>> >>>> On Thursday, May 21, 2026 at 7:13:44 AM UTC-7 WeatheredScientist wrote: >>>> >>>>> I think it's interesting how far the LLM enabled me to go. Just >>>>> setting up the configs was interesting, I saw it make a lot of the same >>>>> errors I would have been likely to make (appending text strings instead >>>>> of >>>>> replacing, for instance). >>>>> >>>>> Ultimately, it's working, and I've shared it on github and docker. But >>>>> it's fair to challenge what's up there to make it better, and make sure >>>>> there isn't anything unnecessary or sloppy. If anyone is interested in >>>>> helping, I'm open to learning and improving. >>>>> >>>>> On Thursday, May 21, 2026 at 7:38:37 AM UTC-4 Greg Troxel wrote: >>>>> >>>>>> WeatheredScientist <[email protected]> writes: >>>>>> >>>>>> > @Vince, great questions. Keeping in mind, this whole build was >>>>>> heavily >>>>>> > AI-assisted, i used claude to answer some of your questions, but i >>>>>> think >>>>>> > the responses are reasonable. Please challenge if they are slop! >>>>>> >>>>>> Different people have different norms, but I think it's not ok to ask >>>>>> other humans to wade through and fix LLM output. It's usually overly >>>>>> verbose, and wrong in ways that are harder to spot than an actual >>>>>> confused human. >>>>>> >>>>> -- 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 visit https://groups.google.com/d/msgid/weewx-user/828fd3db-4d13-4f7a-8427-e18e5f66beccn%40googlegroups.com.
