HowTos:Deploying on MacOs

Deploying on MacOs

This page was created by Wikiadmin on 2026-07-29. Last edited by Wikiadmin on 2026-07-29.

You can run MDriven Server and MDriven Turnkey directly on macOS for local or native-host deployment by installing the correct .NET runtime, starting both applications, and configuring Turnkey to reach MDriven Server.

Choose a macOS deployment approach

Use this page to choose the deployment path that fits your Mac. The detailed native installation procedure is maintained in Documentation:MDriven Server & MDriven Turnkey On Native MacOs.

Approach	Use it when	Start here
Native macOS	You want MDriven Server and MDriven Turnkey to run directly on the Mac with the .NET runtime.	Documentation:MDriven Server & MDriven Turnkey On Native MacOs
Docker on macOS	You want an isolated, reproducible Ubuntu-based environment managed with Docker Desktop.	Documentation:Docker on MacOS- Installing MDriven Server and MDriven Turnkey on Ubuntu Containers
Docker Desktop setup	You need to install Docker Desktop on an Intel Mac before using a container-based deployment.	Documentation:Deployment: Two Ways To Install Docker Desktop on MacOS Intel

Native macOS deployment

A native deployment runs MDriven Server and MDriven Turnkey as separate .NET applications. Apache is not required for this setup.

Before starting, make sure that you have:

macOS Ventura or later.
Terminal access.
The .NET SDK 8 runtime appropriate to the processor: x64 for an Intel Mac or ARM64 for an Apple Silicon Mac.
Downloaded MDriven Server and MDriven Turnkey packages.

Install and verify .NET

Install the .NET SDK 8 package through Homebrew, then verify that the runtime is available before downloading or starting MDriven components. The native deployment guide uses dotnet --list-runtimes for this check.

For example, the expected outcome is that the command lists a .NET 8 runtime. If it does not, resolve the .NET installation before continuing; MDriven Server and Turnkey cannot start through dotnet without it.

Download and prepare MDriven Server

Download the current MDriven Server package.
Extract it to a directory you control, such as a folder under your home directory.
Remove the macOS quarantine attribute from the extracted binaries. macOS Gatekeeper can otherwise prevent downloaded binaries from running.
Start MDriven Server with the .NET runtime, using the Server command and settings described in Documentation:MDriven Server & MDriven Turnkey On Native MacOs.
Confirm in the Terminal output that MDriven Server has started and is listening on its configured port. The documented local example uses port 5010 and disables HTTPS for the initial setup.

Keep this Terminal window open while you start Turnkey. Stopping the process also stops MDriven Server.

Download, prepare, and start MDriven Turnkey

Download the current MDriven Turnkey package.
Extract it to a directory you control. The extracted folder can include a version-specific name; use the actual extracted name in Terminal commands.
Remove the macOS quarantine attribute from the extracted Turnkey binaries.
Start MDriven Turnkey with the .NET runtime as described in Documentation:MDriven Server & MDriven Turnkey On Native MacOs.
Check the Turnkey startup output for the MDriven Server URL it recognized.

Turnkey provides the web user interface and must be able to contact MDriven Server. In a local example, both processes run on the same Mac, so the Server host is localhost.

Configure the Turnkey-to-Server connection

If Turnkey starts but cannot reach MDriven Server, inspect the connection configuration in the Turnkey installation directory.

Location	Purpose	What to check for a local installation
`App_Data/MDrivenServerOverride.xml`	Holds details for the MDriven Server that Turnkey connects to, including its IP address or domain and port.	Confirm that the host is `localhost` and that the port matches the port on which MDriven Server is listening.
`App_Data/TurnkeySettings.xml`	Turnkey settings file.	Review it together with the URL settings if the configured Server URL is not being used.
`App_Data/turnkey-settings/HardServerUrl.xml`	Can contain a fixed Server URL.	Confirm that a fixed URL does not point to a different host or port than the running MDriven Server.

For example, if Server startup output says it is listening on port 5010, a local Turnkey configuration must point to localhost on port 5010. A mismatch causes Turnkey to start without being able to use the Server.

Verify the deployment

Confirm that the MDriven Server Terminal window reports a successful startup and the configured listening port.
Confirm that the MDriven Turnkey Terminal window reports a successful startup and recognizes the intended MDriven Server URL.
Open the local endpoints configured by your installation in a browser, or test them with curl.
Upload a model before treating the Turnkey user interface as an end-to-end validation.

Turnkey can continue to show a loading page even when its process has started successfully if no model has been uploaded. This is not, by itself, evidence that the Turnkey process failed.

Running after Terminal is closed

The native installation procedure starts MDriven Server and Turnkey in separate Terminal sessions. If you need them to continue after you close Terminal or after a restart, configure a macOS service manager such as launchd for your environment. Ensure that the service uses the same working directories, .NET runtime, Server port, and Turnkey Server URL that you verified manually first.

The provided macOS deployment documentation does not define a supported launchd property-list template. Validate a manual startup and connection before adding service automation.

Apache and HTTPS

The documented native setup does not require Apache. Start with the direct .NET deployment, then introduce a web server or HTTPS configuration only when your deployment requirements call for it. The initial MDriven Server example disables HTTPS and notes that it can be configured later.

For broader platform and hosting choices, see Documentation:Deployment.

MDriven Designer on macOS

This page concerns MDriven Server and MDriven Turnkey, not MDriven Designer. MDriven Designer is a Windows application. Testing on macOS Ventura Intel found that Wine Stable 10.0 could install and launch it with glitches, while Porting Kit installed it but did not launch it; a stable production-ready macOS solution was not established. See Documentation:Installing MDriven Designer on MacOs for the test results and instructions.

Contents