You can start protolinker from your host operating system terminal without a user interface, that is a good approach for when, you already have the configuration file exported and want to run it on the production device.
Each operating system will have some peculiarities to run the protolinker from the terminal, in most cases you will have to go to the folder where it is installed to be able to run it, or add to the operating system path.
Here are some of the command options for protolinker:
Copied!Usage: ./protolinker [options] Protolinker - Protocol Integration Tool Options: -h, --help Displays help on commandline options. --help-all Displays help, including generic Qt options. -v, --version Displays version information. -m, --mode <mode> Run mode: 'cli' or 'gui'. --email <email> User email for login. --password <password> Password for login. --file <file> Path to configuration JSON file.
To start the CLI mode, without the user interface you need to use the -m cli, otherwise it will start as the default with the user interface, if you want you can pass all the necessary parameters at once when you call it from the command line or fill it up as it is requested from the application as well. You will need to inform your credentials for your protolinker account (email and password) and the file path to the configuration you want to run.
Note: Once you input all of that the protolinker will create all of your protocols, tags, links and so on and will start the connections, so make sure you have everything connected to your machine before that.
Note: On macOS, if you do not have it added on the path of your system, you will have to open the terminal inside the protolinker.app and go to contents/MacOS to have access to the protolinker binary and run it from the terminal.
