TurnkeySettings
No edit summary
No edit summary
Line 2: Line 2:
The TurnkeySettings.xml is a settings file in the App_Data folder of the Turnkey application. This file holds a number of settings that control the behavior of your application.
The TurnkeySettings.xml is a settings file in the App_Data folder of the Turnkey application. This file holds a number of settings that control the behavior of your application.


=== Using the portal ===
=== Using the Portal ===
The TurnkeySettings.xml is recreated for your application by the portal.mdriven.net when you press SendSettingsAndRestart. The TurnkeySettings is thus normally a generated file based on the settings you have given your application in portal.mdriven.net.
The TurnkeySettings.xml is recreated for your application by the portal.mdriven.net when you press SendSettingsAndRestart. The TurnkeySettings is thus a normally generated file based on the settings you have given your application in portal.mdriven.net.


==== Local installation (not using the portal) ====
==== Local Installation (not using the portal) ====
When you have a standalone or local installation that the portal cannot reach you will need to supply this file yourself.
When you have a standalone or local installation that the portal cannot reach, you will need to supply this file yourself.


==== TurnkeySettingsExtra.xml ====
==== TurnkeySettingsExtra.xml ====
Starting from July 2019 we allow for a TurnkeySettingsExtra.xml file to be created.
From July 2019, we allow for a TurnkeySettingsExtra.xml file to be created.


This file will not be touched / created by the portal. The TurnkeySettingsExtra.xml will be read prior to the TurnkeySettings.xml file is read.
This file will not be touched/created by the portal. The TurnkeySettingsExtra.xml will be read prior to the TurnkeySettings.xml file being read.


The use-case for TurnkeySettingsExtra.xml is that you may have settings local to your application that the portal does not know about - like experimental or new settings not available in portal.
The use-case for TurnkeySettingsExtra.xml is that you may have settings local to your application that the portal does not know about - like experimental or new settings not available in the portal.


One such example at the time of writing is the [[ORCID]] authentication settings that we suspect will be used by very few and thus should not consume portal space and should not increase portal complexity for the user.
One such example at the time of writing is the [[ORCID]] authentication settings that we believe very few will use and thus should neither consume portal space nor increase portal complexity for the user.


Furthermore the TurnkeySettingsExtra allows to set local app name - not overwritten by SendSettings:
Furthermore, the TurnkeySettingsExtra allows to set the local app name - not overwritten by SendSettings:
  <ApplicationNameAsMenu>false</ApplicationNameAsMenu>  -- this prevent the ApplicationName to be added as a index link after the AppLogo in the menubar
  <ApplicationNameAsMenu>false</ApplicationNameAsMenu>  -- this prevent the ApplicationName to be added as a index link after the AppLogo in the menubar


==== Some of settings available in the TurnkeySettings.xml file ====
==== Some of the Settings Available in the TurnkeySettings.xml file ====
  <HidePasswordLogin>
  <HidePasswordLogin>
   False
   False
Line 44: Line 44:
  name of viewmodel to bring up when user click logged in name
  name of viewmodel to bring up when user click logged in name
  </CurrentUserViewModel>
  </CurrentUserViewModel>
[[Category:MDriven Turnkey]]
[[Category:MDriven Turnkey]]

Revision as of 11:35, 17 February 2023

Introduction

The TurnkeySettings.xml is a settings file in the App_Data folder of the Turnkey application. This file holds a number of settings that control the behavior of your application.

Using the Portal

The TurnkeySettings.xml is recreated for your application by the portal.mdriven.net when you press SendSettingsAndRestart. The TurnkeySettings is thus a normally generated file based on the settings you have given your application in portal.mdriven.net.

Local Installation (not using the portal)

When you have a standalone or local installation that the portal cannot reach, you will need to supply this file yourself.

TurnkeySettingsExtra.xml

From July 2019, we allow for a TurnkeySettingsExtra.xml file to be created.

This file will not be touched/created by the portal. The TurnkeySettingsExtra.xml will be read prior to the TurnkeySettings.xml file being read.

The use-case for TurnkeySettingsExtra.xml is that you may have settings local to your application that the portal does not know about - like experimental or new settings not available in the portal.

One such example at the time of writing is the ORCID authentication settings that we believe very few will use and thus should neither consume portal space nor increase portal complexity for the user.

Furthermore, the TurnkeySettingsExtra allows to set the local app name - not overwritten by SendSettings:

<ApplicationNameAsMenu>false</ApplicationNameAsMenu>  -- this prevent the ApplicationName to be added as a index link after the AppLogo in the menubar

Some of the Settings Available in the TurnkeySettings.xml file

<HidePasswordLogin>
  False
</HidePasswordLogin>
<AllowUserToChooseSocialLoginEmail>
  True
</AllowUserToChooseSocialLoginEmail>
<SkipExternalAccountConfirmationScreen>
  False
</SkipExternalAccountConfirmationScreen>
<UseCSSGridByDefault>
  True
</UseCSSGridByDefault>
<HideRegistration>
  True
</HideRegistration>
<CurrentUserViewModel>
name of viewmodel to bring up when user click logged in name
</CurrentUserViewModel>
This page was edited 49 days ago on 03/26/2024. What links here