AntidoteDB
  • Overview
  • Quickstart
  • Examples & Applications
    • Timeseries Load Generator
    • Antidote Web Shell
    • Calendar App
    • Todo List App
  • Tutorials
    • Java Tutorial
  • Related Projects
  • Architecture
    • Overview
    • Ring
    • Log
    • Materializer
    • Transaction Manager
    • Inter-DC Communication
    • Failure Modes
    • Datatypes in Antidote
    • Commit Hooks
    • Features Configuration
  • Deployment
    • Natively (Linux)
    • Local Docker Setup
    • Docker Compose Setups
    • Docker Swarm
    • Kubernetes
  • Monitoring
    • Prometheus and Grafana
  • API
    • Native (Erlang)
    • Protocol Buffer API
    • Erlang
    • Java
    • JavaScript
    • Go
    • Python
  • Benchmarking
    • Setup
    • Basho Bench
  • Tools
    • Logs and Cache Dump
  • Development
    • Setup & Environment
    • Building a Release
    • Testing
    • Contributing
    • Archived Works
  • Release Notes
    • 0.2.1
    • 0.1.1
    • 0.0.1
Powered by GitBook
On this page
  1. Deployment

Natively (Linux)

PreviousFeatures ConfigurationNextLocal Docker Setup

Last updated 5 years ago

Antidote is currently supported on the Linux platform and needs Erlang 21 or greater as a runtime dependency.

To get a release, and build Antidote by following the .

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 section.

Example:

$ pwd
.../antidote/_build/default/rel/antidote
$ ls
bin erts-10.5 lib releases

% start antidote with long name and (data and log) directory in the foreground
$ NODE_NAME=antidote@127.0.0.1 ROOT_DIR_PREFIX=antidote@127.0.0.1/ bin/antidote foreground

% start antidote with long name and (data and log) directory in the background and attach a remote console to it
$ NODE_NAME=antidote@127.0.0.1 ROOT_DIR_PREFIX=antidote@127.0.0.1/ bin/antidote start
$ NODE_NAME=antidote@127.0.0.1 bin/antidote remote_console

% stop antidote
$ NODE_NAME=antidote@127.0.0.1 bin/antidote stop

Clients can now interact with Antidote via the default port configuration (see ).

Logs and data can be found in the respective directories in the directory denoted by ROOT_DIR_PREFIX (default: no prefix, current working folder).

setup your environment
building a release guide
Configuring Antidote
Configuration