AntidoteDB
Main Page
GitHub Repo
Syncfree Project
Lightkone 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
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:
1
# compile the project:
2
make compile
3
4
# run the unit tests:
5
make test
6
7
# run the system tests:
8
make systests
9
10
# run the release test:
11
make reltest
12
13
# run dialyzer to check types:
14
make dialyzer
15
16
# run linter
17
make lint
18
19
# open a shell:
20
make shell
21
22
# build a release:
23
make rel
Copied!
Working on dependencies
When working on dependencies of Antidote it can be helpful to use them as
Checkout 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.
It will also recompile all other dependencies, which can be avoided
by patching rebar3
Tools - Previous
Logs and Cache Dump
Next - Development
Building a Release
Last modified
2yr ago
Copy link
Contents
Working on dependencies