It is often difficult and time-consuming to setup a cluster environment for development or production purposes. For this reason, we decided to make an initial setup for you as easy as possible.

Today we’re introducing the first part of our new deployment tool for cloud computing platforms (Edit: now also available: Amazon Web Services and Google Compute Engine):

Part 1: Digital Ocean

We’ve released our first prototype, which deploys an ArangoDB Cluster on Digital Ocean. Just download a single bash script, export your Digital Ocean API Token and watch the tool take care of the rest for you.

export your Digital Ocean API-Token:

create an ArangoDB Cluster on Digital Ocean:

This will create a directory called ./digital_ocean that contains information about the cluster. You can easily get rid of the cluster as well as of the virtual machines by doing

Feel free to try it out! See below for information on how to configure things.

Some background information for the curious

This script will use your access token for Digital Ocean to deploy a number of VM instances running CoreOS. If you do not already have one, it will first create an SSH keypair for you and deploy it to Digital Ocean and your ssh-agent. Once the machines are running the script uses Docker images to start up all components of an ArangoDB cluster and link them to each other. In the end, it will print out access information.

No installation of ArangoDB is needed, not on the VM instances, neither on your machine. All deployment issues are taken care of by Docker. You can simply sit back and enjoy.

The whole process will take a few minutes and will print out some status reports.

Some switches to configure a few things

Use the -h switch to get this help page.


The following environment variables are used:

  • TOKEN : digital ocean api-token (as environment variable)

Optional prerequisites:

  • REGION : site of the server (e.g. -z nyc3)
  • SIZE : size/machine-type of the instance (e.g. -m 512mb)
  • NUMBER : count of machines to create (e.g. -n 3)
  • OUTPUT : local output log folder (e.g. -d /my/directory)
  • SSHID : id of your existing ssh keypair. if no id is set, a new keypair will be generated and transferred to your created instance (e.g. -s 123456)
  • PREFIX : prefix for your machine names (e.g. export PREFIX="arangodb-test-$$-)

Discover more about ArangoDB:

Want to learn more about the possibilities of the ArangoDB?

Take a look at our Documentation, Tutorials and Cookbook recipes.