I’ve run as many as 4 easily on a pi5.  Just set up different x.conf y.conf 
z.conf files each pointing to different db names and public_html trees. 
Then enable/start weewx@x weewx@y weewx@z and so on.

I use pip here for other reasons but no reason it shouldn’t work for a 
packaged installation.

Systemd logging will be annoying by default so you might want to use 
rsyslogd and edit that utility’s conf file and uncomment the lines that 
make each instance log to its own file. Much easier to work out issues in 
one instance only.

If you go the multi route personally I’d not enable/default weewx.conf so 
you’ll remember that you’ll always need to specify which .conf file to run 
against but there aren’t any hard and fast rules.

On Sunday, February 1, 2026 at 1:03:10 PM UTC-8 DR wrote:

> Matthew Wall has a nice article on how to run several instances of WeeWx 
> in a Pi environment.
>
>
> Have one which is stable and doing pretty much what I want it to now, I 
> am hoping to set  up, on the same Rasp Pi 5, another being fed with data 
> from a different station.
>
> It came to mind that with virtual environments being championed as easy 
> to blow away and start fresh without interfering with other stuff 
> running on the Pi, to  set up another virtual environment, install WeeWx 
> again in there and be able to play around without endangering the 
> original setup I've got running.
>
>
> Does this work OK?  Is there an advantage to running one install of 
> WeeWx and several configurations as Mr. Wall outlines in his Wiki 
> discussion on Github?  It was posted late in 2025 so I assume the 
> virtual environments were up and running at the time and the method of  
> using multiple configurations was optimal?
>
> Dale
>
>
>

-- 
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/b491e764-fece-4f21-981b-4402905a9c5an%40googlegroups.com.

Reply via email to