MultiConnectSDK › CLI
4. Link your project
Do this once for each project folder. In a terminal, in your project folder, run:
multiconnect init
It asks for:
| Question | What to enter |
|---|---|
| Access key and secret | The values from Section 3 |
| Deployment | Which one this folder deploys to, if the key is attached to several |
| Build path | The folder or .zip to upload, relative to this folder, such as publish |
| Build command | The command that creates the build, such as dotnet publish -c Release -o publish. Leave it empty if you build separately |
This writes multiconnect.json in the folder. A deployment with separate masters and game servers also asks for the worker build's path and command.
Your key is not written to the folder. multiconnect init keeps it in your user profile, protected so only your login on this computer can read it (see Section 9).
To link the folder to a different deployment, run multiconnect init --force.

