|
|
@@ -18,7 +18,7 @@ The supported data models can be mixed in queries and allow ArangoDB to be the a
|
|
|
|
|
|
Joins and Transactions are key features for flexible, secure data designs, widely used in RDBMSs that you won't want to miss in NoSQL products. You decide how and when to use Joins and strong consistency guarantees, keeping all the power for scaling and performance as choice.
|
|
|
|
|
|
-Furthermore, ArangoDB offers a microservice framework called [Foxx](https://www.arangodb.com/foxx) to build your own Rest API with a few lines of code.
|
|
|
+Furthermore, ArangoDB offers a microservice framework called [Foxx](https://www.arangodb.com/why-arangodb/foxx) to build your own Rest API with a few lines of code.
|
|
|
|
|
|
#### ArangoDB Documentation
|
|
|
|
|
|
@@ -90,6 +90,8 @@ The ArangoDB image provides several authentication methods which can be specifie
|
|
|
|
|
|
Specify your own root password.
|
|
|
|
|
|
+Note: this way of specifying logins only applies to single server installations. With clusters you have to provision the users via the root user with empty password once the system is up.
|
|
|
+
|
|
|
### Command line options
|
|
|
|
|
|
In order to get a list of supported options, run
|
|
|
@@ -100,6 +102,8 @@ unix> docker run -e ARANGO_RANDOM_ROOT_PASSWORD=1 %%IMAGE%% arangod --help
|
|
|
|
|
|
## Persistent Data
|
|
|
|
|
|
+ArangoDB supports two different storage engines as of ArangoDB 3.2. You can choose them while instanciating the container with the environment variable `ARANGO_STORAGE_ENGINE`. With `mmfiles` you choose the classic storage engine, `rocksdb` will choose the newly introduced storage engine based on [rocksdb](http://rocksdb.org/). The default choice is `mmfiles`.
|
|
|
+
|
|
|
ArangoDB use the volume `/var/lib/arangodb3` as database directory to store the collection data and the volume `/var/lib/arangodb3-apps` as apps directory to store any extensions. These directories are marked as docker volumes.
|
|
|
|
|
|
Please note that the old version 2.x used `/var/lib/arangodb` and `/var/lib/arangodb-apps`. We will refer to the 3.x variant in this document. In case you are starting a 2.x image just replace it with the 2.x variant.
|
|
|
@@ -144,3 +148,11 @@ unix> docker run -d --name arangodb-persist -v /var/lib/arangodb3 busybox true
|
|
|
### Using as a base image
|
|
|
|
|
|
If you are using the image as a base image please make sure to wrap any CMD in the [exec](https://docs.docker.com/engine/reference/builder/#cmd) form. Otherwise the default entrypoint will not do its bootstrapping work.
|
|
|
+
|
|
|
+When deriving the image, you can control the instanciation via putting files into `/docker-entrypoint-initdb.d/`.
|
|
|
+
|
|
|
+- *.sh - files ending with .sh will be run as a bash shellscript.
|
|
|
+- *.js - files will be executed with arangosh. You can specify additional arangosh arguments via the `ARANGOSH_ARGS` environment variable.
|
|
|
+- dumps/ - in this directory you can place subdirectories containing database dumps generated using
|
|
|
+ [arangodump](https://docs.arangodb.com/latest/Manual/Administration/Arangodump.html).
|
|
|
+ They will be restored using [arangorestore](https://docs.arangodb.com/latest/Manual/Administration/Arangorestore.html).
|
Wilfried Goesgens