MultiConnectSDK › CLI
9. The multiconnect.json file
multiconnect init writes this file. It says which deployment the folder goes to and how to build it. It is safe to commit, and committing it is what lets your CI deploy.
Script 9.1: multiconnect.json
{
"DeploymentId": "(from the dashboard)",
"DeploymentName": "my-game-server",
"DeploymentType": "Server",
"IsMasterWorker": false,
"BuildPath": "publish",
"BuildCommand": "dotnet publish -c Release -o publish",
"WorkerBuildPath": null,
"WorkerBuildCommand": null,
"RollbackOnFailure": true
}
| Field | What it holds |
|---|---|
DeploymentId, DeploymentName, DeploymentType |
The linked deployment |
IsMasterWorker |
Whether it takes two builds |
BuildPath, BuildCommand |
The build to upload, and how to make it |
WorkerBuildPath, WorkerBuildCommand |
The same for the game server build |
RollbackOnFailure |
Whether to restore the previous build after a failed rollout |
A deployment's settings are not in this file. They stay on MultiConnectCloud, so the dashboard and the CLI cannot disagree.
Your access key is not in this file either. multiconnect init keeps it in your user profile, one entry per deployment:
| System | Where | Protection |
|---|---|---|
| Windows | %LOCALAPPDATA%\MultiConnect |
Encrypted for your Windows login |
| macOS and Linux | ~/.config/multiconnect |
A folder only your user can open, with the key encrypted |
Run multiconnect init again on each computer you deploy from.

