Suggestion: On CMX updates, provide an option for only those files that were updated from the previous release

[BigOkie]

I have done some modifications to the interface (small ones, mainly having to do with having the WC block change to heat index which required modifying the index.html and the dashboard.js, as well as my menu.js mods). The problem is the entire package destroys those mods if I just overwrite it. There are times I'm unsure as to whether or not I need to replace those files, so I wind up having to redo my modifications, or I have to check the file carefully and then re-insert my modifications. Now, the toughest one is for the WC/HI block on index.html.

How difficult would it be to just generate a differential update as well as the full update?

Thank you!

[SamiS]

Once upon a time in history, there was a list of changed files provided with the release announcement. People did often do only partial updates, missed some files, and that generated a lot of false bug reports and confusion to the forum. Looking from this perspective, I’m afraid that Mark will not support this.

However, there is already an easy way to see which files are changed. You just have to compare the hash_md5 file from your old version and the version you are upgrading to. I use this on every upgrade to find changes regarding the website files that I have translated to my native language.

[HansR]

Agree with @SamiS: differential updates have proven to require too much of support in troubleshooting.

The interface updating is at your own risk I guess. If you want that just draw a copy of the sources and develop a thread yourself? The burden for personal wishes should not be on development.

But what changes did you make? You never know what can be done.

[Dador]

Fortunately, CMX updates come at quite affordable time intervals. Not too fast, not too slow.

Personally, I also have modified files that I compare with the new ones. I use Total Commander for this and its great function - compare by content. Then I overwrite "my" file only with the changes made by Mark. It takes a while, but I've been doing it this way for a long time and it's ok.

[rogerthn]

My update procedure since SOME TIME

Session1:
sudo rsync -av --delete CumulusMX/ CumulusMX_nnnn/

Session 2:
Ctrl-C to terminate running version

Session1:
sudo rsync -av --delete CumulusMX/ CumulusMX_nnnn/
unzip -o CumulusMXDistnnnn.zip

Session 2:
sudo mono CumulusMX.exe -debug

Fairly easy to roolback if needed

[freddie]

I do similar:

Code: Select all

wget (new release URL)
systemctl stop CumulusMX
mv CumulusMX CumulusMX_nnnn
unzip (downloaded new release)
cd CumulusMX_nnnn
cp -a cumulus.ini ../CumulusMX/
(repeat above line for data and backup directories, plus customised templates etc)
systemctl start cumulusmx

The whole thing takes a couple of minutes, and would be done in seconds if I scripted it

[HansR]

@rogerthn @freddie:
And how do you account for modified sources? As that is @BigOkies issue, you would need an automated diff of some kind and move the found lines to the new file - if that is still possible and the changes are not too big. You would need a kind of rewrite git merger. I think it is a pretty complex point.

[rogerthn]

@rogerthn @freddie:
And how do you account for modified sources? As that is @BigOkies issue, you would need an automated diff of some kind and move the found lines to the new file - if that is still possible and the changes are not too big. You would need a kind of rewrite git merger. I think it is a pretty complex point.

Should be possible using diff -e and then ed, some details on https://www.computerhope.com/unix/udiff.htm

[BigOkie]

I mean really, the only reason I have made the modification is to ensure that once it's warm enough to display heat index (in the US that's 80 degrees F and above) the dashboard does this. Once it drops below it I have it revert to wind chill. Maybe adding an option programmatically to do this could be an alternative depending on the LOE.