AntidoteDB
Main PageGitHub RepoSyncfree ProjectLightkone Project
Search…
Overview
Quickstart
Examples & Applications
Tutorials
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
Natively (Linux)
Antidote is currently supported on the Linux platform and needs Erlang 21 or greater as a runtime dependency.
To get a release, setup your environment and build Antidote by following the building a release guide.
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.
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
$ [email protected] [email protected]/ bin/antidote foreground
​
% start antidote with long name and (data and log) directory in the background and attach a remote console to it
$ [email protected] [email protected]/ bin/antidote start
$ [email protected] bin/antidote remote_console
​
% stop antidote
$ [email protected] 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).
Architecture - Previous
Features Configuration
Next - Deployment
Local Docker Setup
Last modified 2yr ago
Copy link