On Tue, 18 Nov 2025 at 17:26, p q <[email protected]> wrote: > DB, I would use postgres but no matter what, the server would be on a > different machine than weewx or possibly >
This is a bit of a red herring unless and until some geek with an itch generates a PR for weeWX to support the pgSQL API. That's assuming Tom would even accept it, and not require it to be turned into an extension. Tom has already stated he should have just made the core program and everything else should have been an extension, that includes SQLite functionality I assume... I'm curious why you'd want, or even consider, splitting the storage and weeWX on separate physical systems? Containers I understand as they usually get used in a fashion akin to a single program and not much else, but using containers on the same system it would still be easy to control the order things are started, multiple physical systems, not so much... > in a container. Regardless I d need a different startup process than with > sqlite. > You would still need some kind of middle-ware library to handle the file or API, just as already happens with both SQLite and MariaDB, I very much doubt weeWX will never have raw support for any storage method... As far as I know weeWX has no code to do raw processing of anything, not even the config files... weeWX uses libraries to handle the content of config files, and parsing config files would be a much easier undertaking compared to something as complicated as a SQLite file... Why would Tom reinvent the wheel when others have produced very robust and extensively tested libraries? -- 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/CAGTinV6pD3HJyHQOmq4ZCCE46x7WikcKPS6MxA-NDs9ZSdo1Tg%40mail.gmail.com.
