fix: detect RatOS 2.1+ as operating system and exit

[dw-0]

Signed-off-by: Dominik Willner th33xitus@gmail.com

[miklschmidt]

Just for future reference to anyone who may come across this, i requested this check to avoid people unknowingly breaking their RatOS installations. KIAUH and RatOS share many of the same goals, and there are plenty of opportunities for future symbiosis which we should definitely pursue, but it requires some devops investment on RatOS's part to get to a place where things can be installed and uninstalled at will etc, it is definitely worth it however and it fits in perfectly with future goals. Thank you @dw-0 for being so accommodating and thank you for all you've done for the community, KIAUH is a staple of the klipper ecosystem for good reason and so this is not a goodbye, but a "see you soon"! I'll be in touch :)

[smwoodward]

@dw-0 yeah I brought this up to Mikkel a while back but he ignored me because I was also calling out his inaccuracies about canbus.

[smwoodward]

@dw-0 best I can remember, kiahu replaces the upstream.conf file. I think the fix would be to do a sed to add the lines needed with kiauh instead of replacing the file should fix it.

[dw-0]

RatOS requires a custom upstreams.conf and uses a custom mainsail nginx config. Both files are modified so that it works on RatOS and its own webapps. Mikkl and i decided to take this step until we figure out a proper way to implement compatibility.
Of course i could have some additional checks in place and use their special file content when running on RatOS, but i respect Mikkls decision which was to disable KIAUH completely for now on RatOS 2.1+

[smwoodward]

Correct, I found this issue shortly after 2.1 was released, and discovered it was the upstream.conf file that changed and stopped the custom pages from working. I haven't looked deeply into the differences between the files that 2.1 needs and the changes kiauh does. That is the suggestion that I was giving to use sed to add what is needed without a full replacement of nginx's config files. Is that what kiauh does is replace the files from the script or does it change the contents of the file?

[smwoodward]

And if I'm not mistaken, when I discovered this issue and replaced the upstream.conf file with the original one with ratos, I didn't change any other files for mainsail and both have been working properly. I can double check that a bit later today to make sure if there was any other changes that I made to make it work with both fluidd and mainsail.

[smwoodward]

RatOS requires a custom upstreams.conf and uses a custom mainsail nginx config. Both files are modified so that it works on RatOS and its own webapps. Mikkl and i decided to take this step until we figure out a proper way to implement compatibility. Of course i could have some additional checks in place and use their special file content when running on RatOS, but i respect Mikkls decision which was to disable KIAUH completely for now on RatOS 2.1+

Ok so I went back and looked at the changes that I made to get it working, and the only change I made was to add

upstream configurator {
ip_hash;
server 127.0.0.1:3000;
}

back to upstream.conf after installing fluidd with kiauh as I put here #478. Since I wasn't needing to make any changes to mainsail, there wasn't any need to run the mainsail portion. Best I can tell the only differences between the kiauh's version of the sites-available/mainsail and RatOS's version is RatOS has listen 80 default_server and a location=/vcore.log section that kiauh's only has listen 80. When I brought this up in RatOS discord I was told that RatOS is designed to use mainsail and dismissed after that.

Since it was kiauh that changed the operation of this, that's why I posted the issue here.

Correct me if I'm wrong, but does kiauh do a check for existing nginx files if doing an install of mainsail or fluidd? If it does, it does look like the operation is to copy over the preconfiged files, such as site-avaliable/mainsail or fluidd and the preconfigured upstream.conf. This is where I suggested, to keep kiauh from breaking RatOS or any other preconfigured Klipper OS that may already exist or will exist in the future, it might be better for kiauh to parse through the existing files and only add missing sections with the sed command instead of over writting the file as it exists, and only copy the preconfigured file over if the file is missing completely.

However I do believe that Mikkel will dismiss anything I suggest because of the history I have with him.