Documentation:LocalServers

LocalServers is a concept where you run the MDrivenServerCore and MDrivenTurnkeyServerCore editions locally.

MDrivenServer is the backend server responsible for OR-Mapping, Maintaining SQL evolve, ServerSide jobs etc

MDrivenTurnkey is the Frontend server responsible for UI and Rest services.

What LocalServers functionality does is:

1. Ensure download of latest versions of the .netCore3.1 self contained versions of the tehe 2 server components. The result ends up on local disk here:\My Documents\MDrivenServers\ with files named MDrivenServerCore.zip and MDrivenTurnkeyCore.zip
2. You can now create complete local server environment locally by adding a new Local-Server-Pair. This local install is given a name and ends up here: My Documents\MDrivenServers\<TheNameOfTheInstall> . under this folder you will find MDrServer and MDrTurnkey
3. Inside each My Documents\MDrivenServers\<TheNameOfTheInstall> \MDrServer folder you will find the full self contained .net core3.1 executable of the webserver for MDrivenServer.
   1. You can start the AppCompleteGenericCore.exe and it will start to function on the port given in the UI
   2. For MDrivenServer the data is stored in a CompactDB that is found here MDrServer\App_Data\DatabaseCompact.sdf
   3. The default database has a user with name "a" and password "123456" - we suggest you leave that as is for local development
4. Inside each My Documents\MDrivenServers\<TheNameOfTheInstall> \MDrTurnkey folder you will find the full self contained .net core3.1 executable of the webserver for MDrivenTurnkey.
   1. The Turnkey server needs to find an MDrivenServer in order to find model and data - the configuration is found in MDrTurnkey\App_Data\MDrivenServerOverride.xml and looks like this:

<?xml version="1.0" encoding="utf-8"?> 
<root>
  <MDrivenServerOverride MDrivenServerPWD="123456">https://localhost:5000</MDrivenServerOverride> 
</root>

The LocalServers-UI in MDrivenDesigner handles this configuration for you.

How does this LocalServer-logic differ from LocalTurnkeyPrototyper?

The LocalTurnkeyPrototyper starts up the TurnkeyCore install (same as discussed above) with this kind of configuration:

<?xml version="1.0" encoding="utf-8"?> 
<root>
  <MDrivenServerOverride PrototypeWithMDrivenDesignerInPath="C:\<PathToModlrFile>.Modlr" CopyAssetsTKOnStart="True"/>
</root>

This configuration makes the TurnkeyServer to act alone without an MDrivenServer - using xml persistence and the model is taken from the provided modlr or ecomdl file. This is a quick way to see how UI will turn up in html - the roundtrip does not require model upload and database evolve - but it does not support ServerSide actions and true database behaviour.