Antidote is currently supported on the Linux platform and needs Erlang 21 or greater as a runtime dependency.
Copy the release folder to the deploy target and start the release binary
bin/antidote with the node name configured via the OS variable
NODE_NAME (long). Other possible configurations can be found in the Configuring Antidote section.
$ pwd.../antidote/_build/default/rel/antidote$ lsbin erts-10.5 lib releases% start antidote with long name and (data and log) directory in the foreground$ NODE_NAMEfirstname.lastname@example.org ROOT_DIR_PREFIXemail@example.com/ bin/antidote foreground% start antidote with long name and (data and log) directory in the background and attach a remote console to it$ NODE_NAMEfirstname.lastname@example.org ROOT_DIR_PREFIXemail@example.com/ bin/antidote start$ NODE_NAMEfirstname.lastname@example.org bin/antidote remote_console% stop antidote$ NODE_NAMEemail@example.com bin/antidote stop
Clients can now interact with Antidote via the default port configuration (see Configuration).
Logs and data can be found in the respective directories in the directory denoted by
ROOT_DIR_PREFIX (default: no prefix, current working folder).