Re: [mh] MQTT Not Reliable

Here's an idea I use ...

When I launch MH, I launch $HOME/mh/bin/mh. So $Pgm_Root is 
$HOME/mh/bin. My local code (e.g. code_dir, data_dir, in mh.ini 
terminology) point to $HOME/local/code, $HOME/local/data, etc. 
Specifically, they're not under $HOME/mh.

Here's the trick, $HOME/mh isn't really a directory -- it's a symbolic 
link to $HOME/mh-prod.  Then if I needed to do a major upgrade like you 
do, I'd do the following:
1) Copy $HOME/mh-prod to $HOME/mh-new.
2) Run "git pull" to update all the code in $HOME/mh-new
3) Change the symbolic link to point to $HOME/mh-new.

That way, I can easily fall back (temporarily or permanently) just by 
moving the symbolic link back. If it takes a couple of days to get 
things straight, I can still have normal house operations when I'm not 
working on it.

I also use this if I'm developing major MH code modifications. (Well, 
the one time I did.) Obviously MH needs to be down while I'm moving the 
symbolic link pointer, but it's very handy to be able to just flip back 
and forth between production and test modes.

There's a lot of good stuff in the last 7 hears. Good luck.

-Brian M

On 9/9/23 08:43, Stephen Switzer wrote:
> I'm thinking of updating my MH code today and I started to look at the 
> GIT branch on my MH server... Well!! It appears that I haven't updated 
> anything since 2016!
>
> root@avalanche:/opt/mh# git log
> commit c903c9012d1b86fcd45a6cb61e21e6f88a0c40a2 (HEAD -> running, 
> origin/running)
> Author: Pmatis <[email protected]>
> Date:   Sun Sep 18 13:14:05 2016 -0400
>
>     update running code
>
> I can foresee breaking ALL kinds of things by merging in master 7 
> years later! Not for the faint of heart, so I have to brace myself. LOL
>
> At least it's been really stable, except for my recent MQTT woes!
>
> Steve
>

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users