You can deploy the docker to a variety of devices, e.g., PCs, servers, Raspberry Pi, and so on. A wide range of mainstream operating systems are supported.
After logging in to the device that needs to deploy the docker program, download the corresponding docker program according to the operating system of the device. The download link can be found in the content displayed after clicking the Add a docker manually tab on the Docker page. Deploying the docker program requires 2 parameters to be set:
Configure the “Communication Address” and “FMZ Quant Trading Platform Account Password” when deploying the docker:
Docker for Windows The Windows Interface version of the docker can fill in these two parameters directly to the corresponding input box controls on the docker’s interface.
Command line version of the docker
For other command line versions of the docker program, there are different commands for different operating systems. Using Linux & Mac as an example, use the command: . /robot -s node.fmz.com/123456 -p 654321
, the following describes each part of the command:
. /robot
means to run robot, an executable program (i.e., a docker program), where 123456
is the UID, and 654321
is the password of the FMZ Quant Trading Platform account corresponding to the UID.
The parameter -s
indicates the correspondence address of the UID of the FMZ Quant Trading Platform
, and the value of the parameter can be populated with e.g.: node.fmz.com/123456
.
The parameter -p
indicates the “password for the UID’s account on the FMZ Quant Trading Platform”, which can be filled with a value such as: 654321
.
Please note that the parameters here are examples, the actual parameters can be viewed after logging into FMZ.COM and clicking on the Add a docker manually tab on the Docker page.
The parameter -p
does not have to be explicitly written in the command to deploy the docker, you can use the . /robot -s node.fmz.com/123456
command to run it, and then you will be prompted for a password, which you can then enter manually.
In addition, pay attention to issues such as permissions to execute the program, and give the docker program enough permissions to lift the running restrictions.