The firmware is put to /var/www/firmware
on the web server web-ffsh
I need a role that adds a script in /root that will
delete testing and rc dir in case they are not symlinks to safe space
Download the release archives, combine the files and unpack to safe space always delete the archive stuff as soon as it is no longer needed.
Then the unpacked folder needs to be renamed to testing so the link needs to be gone
rc should link to testing.
By default it should download the latest release
But there should be the option to provide the version as argument
Then there should be a promote to stable command that takes testing and moves it to stable
So we have rc stable testing as folders/symlinks and when we promote to stable we remove the stable dir and move testing to stable. Then create symlink testing to stable RC should link to testing. rc as separate stage is not actively used so we just link it.
The promote to stable should check if the version change is significant so if the first version changed but also minor so 2025.1.2.0
2025 major
1 minor
2 patch
0 ffsh extra digit
Patch and extra digit do not matter but with the others it should ask the user if he is sure because it is a bigger change and if a copy to the archive was created. It should always regardless ask are you sure.
The output of the script should be nice, animated of possible and mobile friendly so terminal on small screen
If you have any questions ask them first don't assume stuff
The role should be later only be deployed on the Webserver maybe we need a special check and skip otherwise
The firmware is put to /var/www/firmware
on the web server web-ffsh
I need a role that adds a script in /root that will
delete testing and rc dir in case they are not symlinks to safe space
Download the release archives, combine the files and unpack to safe space always delete the archive stuff as soon as it is no longer needed.
Then the unpacked folder needs to be renamed to testing so the link needs to be gone
rc should link to testing.
By default it should download the latest release
But there should be the option to provide the version as argument
Then there should be a promote to stable command that takes testing and moves it to stable
So we have rc stable testing as folders/symlinks and when we promote to stable we remove the stable dir and move testing to stable. Then create symlink testing to stable RC should link to testing. rc as separate stage is not actively used so we just link it.
The promote to stable should check if the version change is significant so if the first version changed but also minor so 2025.1.2.0
2025 major
1 minor
2 patch
0 ffsh extra digit
Patch and extra digit do not matter but with the others it should ask the user if he is sure because it is a bigger change and if a copy to the archive was created. It should always regardless ask are you sure.
The output of the script should be nice, animated of possible and mobile friendly so terminal on small screen
If you have any questions ask them first don't assume stuff
The role should be later only be deployed on the Webserver maybe we need a special check and skip otherwise