Skip to main content
Open

Placeholder config files to make updates easier.

Related products:Universal GUIIndicium Service Tier
htimmermans
Harm Horstman
Robbert van Tongeren
+28
  • htimmermans
    htimmermans
  • Harm Horstman
    Harm Horstman
  • Edwin Saan
  • Ricardo
  • Robbert van Tongeren
    Robbert van Tongeren
  • Michael
    Michael
  • Bart Metselaar
    Bart Metselaar
  • Benjamin Westra
  • Dennis van Leeuwen
    Dennis van Leeuwen
  • John Lunenburg
    John Lunenburg
  • Raoul van der Vleuten
  • Freddy
    Freddy
  • Arno Rouwenhorst
    Arno Rouwenhorst
  • Frank Junger
  • Remco Kort
    Remco Kort
  • Marcel van Langen
    Marcel van Langen
  • Robert Egberts
  • Arie V
    Arie V
  • J. de Lange
    J. de Lange
  • mperrott
    mperrott
  • Suleyman
  • C. Lousberg
    C. Lousberg
  • Rick
  • Matthijs ter Stege
    Matthijs ter Stege
  • Kevin Rosink
    Kevin Rosink
  • HarryA
  • Denniss
  • Remco Duijsens
    Remco Duijsens
  • Marius Korff
    Marius Korff
  • Hans Pot
  • Guido Bijl
    Guido Bijl
  • rbiram
    rbiram
  • Eric
    Eric

Bas
Vanguard
  • Vanguard
  • 19 replies

Instead of including config.json, web.config and appsettings.json files that break my instance after installing an update include them with a default_ or example_ prefix.

That way I can just take the folder with the new Universal files and have someone paste them over the old ones. Now I constantly need to assist the IT staff because we don’t have access to the application servers.

You should only need to touch settings files at the original point of installation and when something changes in said settings. 

Did this topic help you find an answer to your question?

5 replies

Jasper
Superhero
  • 678 replies
  • November 10, 2020
Updated idea status NewOpen

Forum|alt.badge.img+15
  • Superhero
  • 196 replies
  • November 17, 2020

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

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


Bas
Vanguard
Forum|alt.badge.img+3
  • Author
  • Vanguard
  • 19 replies
  • March 21, 2023

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.


Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil
  • 533 replies
  • March 21, 2023

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


mperrott
Hero
Forum|alt.badge.img+12
  • Hero
  • 99 replies
  • March 24, 2023

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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings