The MDriven Portal is the web site where MDriven Turnkey application owners register and manage application metadata, settings, deployment-related actions, and development links.
Go to portal.mdriven.net and sign in with your MDriven account.
What you can do in the Portal
Use the Portal to find and manage the Turnkey sites associated with your account. From an application's management pages, you can work with settings and open links to development and diagnostic information.
| Task | What the Portal provides | More information |
|---|---|---|
| Open an application | Sign in, open your apps, and select the Turnkey site you want to manage. In the Portal, the site list is available through Views â Show my Turnkey sites. | Getting started |
| Start the current MDriven Designer | Start MDriven Designer through the Portal's ClickOnce link so that it refreshes to the latest version before it starts. | Documentation:Starting MDriven Designer from the portal |
| Update Turnkey settings | Enter settings for the application and use Send Settings and Restart. This recreates TurnkeySettings.xml for the application from the settings stored in the Portal.
|
Documentation:TurnkeySettings |
| Configure external sign-in | Add supported external-login client IDs and secrets to the application's Portal settings, then use Send Settings and Restart. | Documentation:External login services in MDriven Turnkey |
| Configure email | Change the email settings used by server-side jobs in the MDrivenServer used by the Turnkey site. | Documentation:Turnkey email settings |
| Inspect generated bindings | Open the application's development information and select a ViewModel to inspect the generated AngularJS and MVC binding suggestions. | Documentation:Bindings for angular |
| Open logs | Use the direct Turnkey log links on the application's Portal management page. | Documentation:Turnkey and MDrivenServer logs |
Open and manage a Turnkey site
- Go to portal.mdriven.net and sign in.
- Open Views â Show my Turnkey sites.
- Select the application you want to work with.
- Use the application's available management pages for the task at hand. For example, open development information when you need generated bindings, or open the settings page before selecting Send Settings and Restart.
The Portal holds metadata about your application; it does not run the application itself. If you provide an Azure publishing profile, the Portal can refresh the Turnkey installation by deploying new versions.
Keep your model outside the Portal
The Portal does not keep a copy of your model. Keep the model in your own source-control repository and retain copies that you can restore.
For example, if you deploy a changed model and later need to return to an earlier version, recover that version from your repository rather than expecting the Portal or the running server to be the only copy.
Apply settings safely
When you select Send Settings and Restart, the Portal recreates the application's App_Data/TurnkeySettings.xml. Do not treat that generated file as the place for settings that must survive a Portal-driven refresh.
Use the settings-file mechanism documented in Documentation:TurnkeySettings for settings that the Portal does not manage:
TurnkeySettingsExtra.xmlis read beforeTurnkeySettings.xml.TurnkeySettingsOverride.xmlis read afterTurnkeySettings.xml.
For example, keep an application-specific setting that is not represented in the Portal in one of these supplementary files, as appropriate, rather than editing the generated TurnkeySettings.xml and losing the change on the next settings update.
Development information and bindings
The application's development information can show the rendered output and pre-generated binding snippets for a selected ViewModel. This is useful when you need to see how a ViewModel's variables, types, visibility, grid rows, or actions are expressed for the client.
For example, select a ViewModel in development information to inspect the binding produced for a grid or the expression that controls whether a UI element is visible. Use this output to understand the rendered result and as a starting point when working with AngularJS or MVC bindings. See Documentation:Bindings for angular for the binding details.
Diagnose a running application
The Portal management page provides direct links to Turnkey log pages. Use them when you need to investigate an application issue, then consult Documentation:Turnkey and MDrivenServer logs for direct log URLs, MDrivenServer log locations, Azure SCM access, and command-line log viewing.
If you need server and environment details, see Documentation:Serverinfo.