Placeholder config files to make updates easier.

If you use Indicium on Azure as an App Service, you can apply a workaround for appSettings.json. It's explained here:

• Azure Indicium(Universal) appsettings.json encryption of the DB username and password

The values in appSettings.json are overwritten by the settings defined in the Azure portal.

Client just deployed a new version and overwrote the config file. 

Have the config file in the deployment named config_default or something would be very benifitial.

This also goes for the custom.css and manifest.json

Just my 2 cents, from my Azure deployments trying to make it as less time consuming. More can be automated but due to time constraints i came up with below.

Pre-requisite:

Create a folder containing the constant files of Universal as Universal_files. ie. Icons, configs, etc

Create a folder containing the constant files of Universal as Indicium_files. ie. Icons, configs, etc

Create a pre-upgrade script that cleans the folder of Universal/Indicium (rm -rf *)

Create a post-upgrade script that copies the constant files from *_files to the related folder. ie. Copy from Universal_Files to wwwroot, Search and replace Thinkwise in html, etc

Best Practice execution flow:

1. Stop the App Service
2. Go to Kudu
3. Run the Pre-Upgrade
4. Drag & Drop the  GUI Zip in relevant folder
5. Run the Post-Upgrade as soon as the zip are extracted by Kudu
6. Start the App Service

As Rene already mentioned configs in Azure are in the App service so they are more safe there than in a file.