Updated Upgrade from old versions (markdown)

Upgrade-from-old-versions.md

@@ -1,4 +1,114 @@
-You can upgrade from older installations of this same script by using the following steps.
+Although we suggest to start from a clean install, since that will integrate the latest changes you can upgrade from older installations of this same script by following some of these recommendations.
 
 ## From unstable to stable
-We have changed to default to the 
+In previous versions we used the unstable branch, since that we have changed to default to the stable version of the repository.
+Make sure to change the repository from unstable to stable so it looks like this,
+
+```
+deb https://download.jitsi.org stable/
+```
+
+## Update our github repository to the latest version
+In case you already have a previous clone of our repository, it's time to get the latest changes, inside the repository folder use,
+
+```
+git pull
+```
+
+## Customization Upgrade
+
+```
+############################### WARNING #################################
+We will not be responsible for any misconfiguration or damage on your setup.
+Only make customization changes if you know what you are doing or if you
+agree with the responsibility you get by modifying your environment setup.
+#########################################################################
+```
+
+One of the reasons we suggest to use make a clean install is because while running the script there are some customization options that make sure you have the features working the way you need it.
+
+
+This options are "memorized" on the files *jitsi-meet.sh*\, and *jm-bm.sh* in case you have selected to use a [custom brandless mode](Custom-brandless-mode).
+
+Make sure you review both files (if applicable) to meet you needs.
+Some of the fields you might want to check more carefully are,
+
+### jitsi-updater.sh
+
+* LOC_REC -> "on"
+
+Enables local recording if previously configured.
+
+* ENABLE_BLESSM -> "on"
+
+Enables the custom brandless mode script to be applied.
+
+### jm-bm.sh
+
+* PART_USER -> "Participant"
+
+
+"Participant" is the default English name holder for any new participant joining the conference, you can tweak this to your own language in case you don't use English.
+
+e.g.: Spanish
+
+```
+PART_USER="Participante"
+```
+
+* LOCAL_USER -> "me"
+
+
+"me" is the default English reference to yourself on the conference, it mush be a small word, we have mentioned before some suggestions might be: yo (Spanish) | je (French) | ich (German).
+
+e.g.: Spanish
+
+```
+LOCAL_USER="yo"
+```
+
+## Update system
+Make sure that your system can upgrade without issues, mainly by GPG errors. 
+Run,
+
+```
+(sudo) apt-get update
+```
+
+In case you get an error by an expired GPG key, you can add it by using the command, where 0101010101010101 is the key not found on your apt key repository.
+
+```
+(sudo) apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0101010101010101
+
+```
+
+If no error found then you can run directly,
+
+```
+(sudo) bash jitsi-updater.sh
+
+```
+
+### Trouble shooting upgrade system
+In some cases you might find issues were the script jitsi-updater.sh doesn't resolve a complete upgrade from old installations, mainly when upgrading from videobrigde version 1 to version 2, and some major jitsi components.
+
+In this case please use apt-get dist-upgrade followed by the jitsi-updater.sh script.
+
+```
+(sudo) apt-get update
+(sudo) apt-get dist-upgrade
+(sudo) bash jitsi-updater.sh
+
+```
+
+## Chrome - Chromedriver
+
+On newer version when using Jibri recording or streaming you might find some labeling stating the automated nature of the process, this can be avoided by 
+
+```
+mkdir -p /etc/opt/chrome/policies/managed
+echo '{ "CommandLineFlagSecurityWarningsEnabled": false }' | sudo tee /etc/opt/chrome/policies/managed/managed_policies.json
+
+```
+
+You can always check the quick_jibri_installer.sh to review any possible update on the changes applied to the installation process.