in V5 i am assuming a single station can be created but separate weewx.conf’s used, as in V4 weewx-multi config, with the downside that they share same extensions.py i.e. not utilising V5’s design change
in my case, i want same codebase and python modules available to all weewx instances but each with own extensions.py, so i have in mind to have a weewx user whose home dir has a single venv (shared codebase with pip install), and station create each instance (has its own extensions.py) i can see the case for separate venv for each station (conflicts, independence) but i don’t require that ⊣GE⊢ > On 1 Sep 2023, at 12:09 am, Tom Hogland <[email protected]> wrote: > > I'm thinking of moving to v5. I have a Tempest and VP2 setup and running a > custom weewx-multi. Seems like two venv setups would be a very simple way to > replicate this... -- 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/6D6A2E62-C98A-4AD6-B834-92C175516408%40geddy.au.
