MultiConnectMultiConnectDocs Website home
MultiConnectSDK › CLI

5. Deploy

multiconnect deploy

This runs your build command, zips the build, uploads it, rolls it out using the deployment's current settings, and waits until it is live.

The first time a build command runs on your computer, the CLI shows it and asks before running it, and it asks again whenever the command in multiconnect.json changes. The build path must be inside the project folder.

Your deployment keeps working during a deploy. The current build keeps serving until every new container is healthy. If the new ones never become healthy, the previous build is restored.

On a server with a grace period, old containers keep running for that time, so connected players are not dropped. The CLI reports success as soon as the new build is live, without waiting for them.

Useful options

Option What it does
--tag v1.4.2 Labels this build, such as a version or commit
--skip-build Uploads what is already at the build path, without running the build command
--no-rollback Leaves a failed rollout in place, so you can inspect it
--no-wait Returns as soon as the rollout starts
--timeout 45 Minutes to wait for the rollout. The default is 30, and the rollout carries on either way
--yes Skips the confirmation question
--approve-build-command Runs the build command without asking, even if it is new on this computer. For CI: check the command first

What the exit code means

Code Meaning
0 The new build is live
1 The build, upload or rollout failed, or the deploy was refused
2 Still rolling out when --timeout ran out. This is not a failure yet, so check with multiconnect status