Updating Sametime 12 to FP1. Not all customizations are kept

Upon suggestion from my friend Erik Schwalb of HCL, I upgraded to FP1 a Sametime12 server where I made some branding customization.

Contrary to what I wrote in my previous post not ALL customizations are kept.

If you made some branding, you will lose it. The directory /sametime-config will be deleted and replaced by a new one, so all the custom branding files in /sametime-config/web/branding will be gone.

Also, not all the settings in custom.env will be kept. If you applied branding adding, e.g.
REACT_APP_PRODUCT_NAME=RoB ST Server
REACT_APP_PRODUCT_LOGO=/images/branding/logo.jpg
those settings will not be kept.

To check which settings are kept, look in install.sh, you will see that the upgrade maintains the default ones, e.g SAMETIME_PROXY_HOST=st.company.com.

If you enabled Let’s Encrypt support in .env you will lose it as well, since the Let’s Encrypt TLS cert in /sametime-config/web/acme-certs/ will be gone.

Again, check install.sh to see which settings are maintained in .env

So, the suggestion I have is to copy the sametime installation directory (you read my previous post, right?) and then after the upgrade copy back the /sametime-config directory and check the files custom.env .env and docker-compose.yml

Thanks a lot to Eric Schwalb for pointing me in this direction, since I didn’t applied customizations at my customer site, I did not notice that some settings are not kept.

Updating Sametime 12 to FP1. A note about integration with email

I have upgraded my customer server to Sametime 12 FP1.

The process is as easy as 1-2-3 🙂 Just unzip Sametime_Premium_12.0_FP1.zip into the existing sametime directory (make a copy before, just in case). Run ./install.sh, it will ask you if you want to upgrade; answer Y and that’s all.
All the customization done in .env and custom.env will be maintained.

There’s a but; if you customized docker-compose.yml, the changes will not be kept, it will be overwritten by a new file.

Since integration with mail require a change in docker-compose.yml, you have either to copy that file from your previous installation (you copied it, right?), or edit it and add again
SAMETIME_EXTERNAL_WARINTEGRATION=true