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

Setup & Environment

Antidote requires Erlang 21 or greater. Make sure the command erl is executable in your console.

Use the following Makefile targets to build and test antidote:

# compile the project:
make compile

# run the unit tests:
make test

# run the system tests:
make systests

# run the release test:
make reltest

# run dialyzer to check types:
make dialyzer

# run linter
make lint

# open a shell:
make shell

# build a release:
make rel

Working on dependencies

  • Create a folder named _checkouts in your antidote folder (next to the _build folder)

  • Clone or symlink the dependency into that folder. The folder name in _checkouts must be the name of the dependency in rebar.config.

  • When running a rebar3 task on Antidote, it will always use the latest version from the dependencies.

PreviousLogs and Cache DumpNextBuilding a Release

Last updated 5 years ago

When working on dependencies of Antidote it can be helpful to use them as :

It will also recompile all other dependencies, which can be avoided

Checkout Dependencies
by patching rebar3