Installing ArangoDB

Any Linux distribution which supports ArangoDB 2.8.11 can be used, and you can see which distributions are supported on the official installation package, along with steps to install, from the official ArangoDB website.


For convenience, we include here the steps for installing on

  • Debian 7, 

  • Debian 8, 

  • Ubuntu 15.10,

  • Ubuntu 16.04, 

  • CentOS 7.


Currently Centro must use ArangoDB 2.8.11. 

Install of ArangoDB for Linux

Make sure you follow the steps for your version of Linux. The same steps are used for updating the ArangoDB engine.

Note

In case the 2.8.11 version of ArangoDB cannot be found, it has been archived by on Arangodb.com at


Please make sure that you run these commands one line at a time, as it might break the process otherwise.


First, you must obtain root access by running

 
su
CODE

And then typing in your root password.


Find the Linux OS and version that suits your environment.

For Debian 8 run the following commands:


wget https://download.arangodb.com/arangodb2/Debian_8.0/Release.key 
 
apt-key add - < Release.key 
 
echo 'deb https://download.arangodb.com/arangodb2/Debian_8.0/ /' | tee /etc/apt/sources.list.d/arangodb.list 
 
apt-get update 
 
apt-get install arangodb=2.8.11
CODE



For Debian 7 run the following commands:


wget https://download.arangodb.com/arangodb2/Debian_7.0/Release.key apt-key add - < Release.key apt-key 
 
add - < Release.key 
 
echo 'deb https://download.arangodb.com/arangodb2/Debian_7.0/ /' | tee /etc/apt/sources.list.d/arangodb.list 
 
apt-get update 
 
apt-get install arangodb=2.8.11
CODE



For Ubuntu 16.04 run the following commands:


curl -O https://download.arangodb.com/arangodb2/xUbuntu_16.04/Release.key

apt-key add - < Release.key 

echo 'deb https://download.arangodb.com/arangodb2/xUbuntu_16.04/ /' | sudo tee /etc/apt/sources.list.d/arangodb.list

 
apt-get install apt-transport-https

apt-get update

apt-get install arangodb=2.8.11
CODE



For Ubuntu 15.10 run the following commands:


curl -O https://download.arangodb.com/arangodb2/xUbuntu_15.10/Release.key

apt-key add - < Release.key 

echo 'deb https://download.arangodb.com/arangodb2/xUbuntu_15.10/ /' | sudo tee /etc/apt/sources.list.d/arangodb.list

 
apt-get install apt-transport-https

apt-get update

apt-get install arangodb=2.8.11
CODE



For CentOS 7 run the following commands:


cd /etc/yum.repos.d/
 
curl -O https://download.arangodb.com/arangodb2/CentOS_7/arangodb.repo
 
yum -y install arangodb-2.8.11
 
firewall-cmd --permanent --add-port=8529/tcp
 
firewall-cmd --reload
CODE



Setting Up EndPoint

After installation, you need to bind the ArangoDB service to listen on all inbound endpoints. You can do this by editing the config file as follows:

cat /etc/arangodb/arangod.conf | sed 's/endpoint = tcp:\/\/127.0.0.1:8529/endpoint = tcp:\/\/0.0.0.0:8529/' > /etc/arangodb/arangod.conf.new ; cp /etc/arangodb/arangod.conf.new /etc/arangodb/arangod.conf 
 
service arangodb restart
CODE


Deploying the Centro Database

Alongside the installation files for Centro, you should find a folder named “Deploy” which contains the necessary scripts to install your Centro database.


After copying the “Deploy” folder to your Linux machine, run the following shell script to deploy the database:

./setup.sh
CODE

You will see some output indicating the deployment steps being carried out.


Congratulations, your Centro database is now deployed! When updates become available, you will be able to use the same setup script to install any updates to your database.


You can view the database from http://<Server-IP>:8529/_db/<Database –Name>/


Where Server-IP is the IP address of the server machine you installed ArangoDB on, and Database-Name is the name you used when deploying the database (ActifyDB by default).


If you do not know the IP address of the machine, you can check it by running:

ifconfig
CODE

The IP address will be under inet addr: in the output of the command. This will be the one which corresponds to the eth0 adapter and not local loopback (i.e. the address should not be 127.0.0.0.1).