|
@@ -828,14 +828,14 @@ elif [ $FORCE ]; then
|
|
|
echo -e "\e[31mPlease rerun the update.sh Script without the --force/-f parameter.\e[0m"
|
|
|
sleep 1
|
|
|
elif [ $NEW_BRANCH == "master" ] && [ $CURRENT_BRANCH != "master" ]; then
|
|
|
- echo -e "\e[33mYou are about to switch your mailcow Updates to the stable (master) branch.\e[0m"
|
|
|
+ echo -e "\e[33mYou are about to switch your mailcow updates to the stable (master) branch.\e[0m"
|
|
|
sleep 1
|
|
|
- echo -e "\e[33mBefore you do: Please take a backup of all components to ensure that no Data is lost...\e[0m"
|
|
|
+ echo -e "\e[33mBefore you do: Please take a backup of all components to ensure that no data is lost...\e[0m"
|
|
|
sleep 1
|
|
|
- echo -e "\e[31mWARNING: Please see on GitHub or ask in the communitys if a switch to master is stable or not.
|
|
|
- In some rear cases a Update back to master can destroy your mailcow configuration in case of Database Upgrades etc.
|
|
|
- Normally a upgrade back to master should be safe during each full release.
|
|
|
- Check GitHub for Database Changes and Update only if there similar to the full release!\e[0m"
|
|
|
+ echo -e "\e[31mWARNING: Please see on GitHub or ask in the community if a switch to master is stable or not.
|
|
|
+ In some rear cases an update back to master can destroy your mailcow configuration such as database upgrade, etc.
|
|
|
+ Normally an upgrade back to master should be safe during each full release.
|
|
|
+ Check GitHub for Database changes and update only if there similar to the full release!\e[0m"
|
|
|
read -r -p "Are you sure you that want to continue upgrading to the stable (master) branch? [y/N] " response
|
|
|
if [[ ! "${response}" =~ ^([yY][eE][sS]|[yY])+$ ]]; then
|
|
|
echo "OK. If you prepared yourself for that please run the update.sh Script with the --stable parameter again to trigger this process here."
|