MultiConnectSDK › CLI
6. What to deploy for each type
Each type expects a particular build. If you use --build-path and --build-command, they fill in the same answers as Section 4.
| Deployment | Build command example | Build path | Notes |
|---|---|---|---|
| .NET server or API | dotnet publish -c Release -o publish |
publish |
The DLL named in Entry Point File must be at the top of the folder |
| Node.js server | npm ci --omit=dev |
. |
Upload it ready to run, with node_modules included. Nothing is installed for you |
| Python server | Your own packaging step | Your build folder | Upload it ready to run, with its packages included. Nothing is installed for you |
| Node.js or Python API | Your own build, if it has one | Your build folder | Include package-lock.json or requirements.txt, because packages are installed for you |
| Unity server | See Section 11 | Your build folder | The binary must match the deployment's Entry Point File |
| Website | npm run build |
dist |
The folder your framework builds. It is served as it is, with no build step |
| Database | Not applicable | Not applicable | A database has no build. status, info, balance and analytics still work |
Check your first deploy's result on the deployment's page on the dashboard. Its Deployment guide shows the layout that type expects.
Master and game servers take two builds, which always deploy together. The dashboard and the CLI call the game server build the worker build.

