Aleph requires multiple services to operate. It uses Docker containers to make it easier for development and deployments. Before we continue, you will need to have Docker and
docker-compose installed. Please refer to their manual to learn how to set up Docker and docker-compose.
Developer mode is a docker configuration for Aleph which makes it easy to do software development and debug the tool without having to install its dependencies on your host machine. These are the features of developer mode:
The code for the backend (api) server and the React frontend will automatically reload to reflect any changes you make in your working copy while the application is running.
Both backend and frontend will operate in debug mode and give more verbose error messages when a problem occurs.
The host machine's file system will be accessible from within Aleph's docker container at
Developer mode overrides the configuration file for
docker-compose.dev.yml instead of
docker-compose.yml. This is done by wrapping most developer mode commands using
As a first step, check out the source code of Aleph from GitHub:
# Use the SSH URL if you have commit access:git clone https://github.com/alephdata/aleph.gitcd aleph/
Once the code is downloaded, find the file called
aleph.env.tmpl in the base directory. This is a template of the configuration file. Make a copy of this file named
aleph.env and define settings for your local instance. Check the configuration section for more information regarding the available options.
Also, please execute the following command to allow ElasticSearch to map its memory:
sudo sysctl -w vm.max_map_count=262144
With the settings in place, you can use
make all to set everything up and launch the web service. This is equivalent to the following steps:
make build to build the docker images for the application and relevant services. You can run
make docker-pull before to pull pre-build release images.
make upgrade to run the latest database migrations and create/update the search index.
make web to run the web-based API server and the user interface.
http://localhost:8080/ in your browser to visit the web frontend.
If any of the above steps fail, refer to the troubleshooting section for some common stumbling blocks and their fixes.
During development, you will need to run command-line operations for certain tasks. In order to do so, you will first need to enter the docker container of Aleph. To do so, run:
make shell# This will result in a root shell inside the container:aleph --help
This will enter a docker container where the
aleph shell command is available (see Usage for details). You can also access the host computers file system at
/host. This means a file stored at
/tmp/bla.txt on your computer can be found at
/host/tmp/bla.txt inside the container.
For development purposes, you can quickly create a new user with the
aleph createuser command, inside a shell:
aleph createuser --name="Alice" \--admin \--password=123abc \firstname.lastname@example.org
If you pass an email address in the
ALEPH_ADMINS environment variable (in your configuration) it will automatically be made into an admin.
createuser, the newly created user's API key is printed, which you can use in the
Authorization HTTP header of requests to the API. If you pass a password, you can use this email address and password to log into the web interface.
If you want to quickly get some sample data in your Aleph instance you can use
crawldir to index a small test data folder.
aleph crawldir /aleph/contrib/testdata
To also get a sample of (non-document) entity data, consider loading sanctions lists.
To run the tests, assuming you already have the
docker-compose up and ready, run:
make testmake ingest-test
This will create a new database and run all the tests.
You can also build the Aleph images locally. This could be useful while working on the Dockerfile changes and new dependency upgrades.
To build the image you can run
make build, which will build the
alephdata/aleph image (this will generate a production ready image).
Aleph is distributed as a set of Docker containers, which can be run on any server that meets the following criteria:
8GB (or more) of RAM. While the software will start with much less, we advise providing ample main memory for ideal performance.
A domain name or IP address which can be used at the root via HTTPS (i.e. Aleph doesn't support running at a sub-path like
/aleph). You are welcome to contribute fixes for this scenario.
An internet connection to download and install the package.
To begin a production deployment:
Make a copy of the configurations file named
aleph.env and define settings for your production instance. Check the section on configuration for more information regarding the available options.
ALEPH_TAG environment variable to specify the version of Aleph you want deploy. If
ALEPH_TAG is not set, the stable version specified in the docker compose file is deployed.
Once you are happy with your configuration, execute the following command to allow ElasticSearch to map its memory:
sudo sysctl -w vm.max_map_count=262144
Finally, you can boot the docker-compose environment:
docker-compose up -d
This will run Aleph in detached mode. You can shut down the system at any time by issuing the following command:
Before Aleph can process any requests or data, you need to make sure it sets up the database and search index correctly by executing an upgrade:
docker-compose run --rm shell aleph upgrade
While the system is running, it will bind to to port
8080 of its host machine and accept incoming connections. You can check that the system is functional with a curl request:
If your servers firewall configuration allows it, you can now also open
http://localhost:8080 in your browser and use the web interface to navigate the application.
The main configuration file of Aleph is
aleph.env, which is loaded by docker-compose and can modify many aspects of system behaviour. A template for the configuration with details regarding many of the options is available in the
You will need to provide a value for the
ALEPH_SECRET_KEY. A good example of a value is the output of
openssl rand -hex 24.
Aleph needs to know the URL under which the web interface is mounted. Make sure to set the correct public
Using OAuth for login is optional. Skip this section (and leave the config commented out) if you don't want to use it.
Aleph supports a couple of OAuth providers out of the box: Google, Facebook and Microsoft Azure.
Save the client ID and the client secret as
Create a new app over at https://apps.dev.microsoft.com, make a note of the KEY and secret you generate there. Callback URL should be as follows: https:///api/2/sessions/callback . Then add the following to aleph.env, remember to update KEY and SECRET with your values.
ALEPH_OAUTH=trueALEPH_OAUTH_KEY=***************************ALEPH_OAUTH_SECRET=***************************ALEPH_OAUTH_NAME=AzureALEPH_OAUTH_BASE_URL=https://login.microsoftonline.com/organizations/oauth2/v2.0/ALEPH_OAUTH_AUTHORIZE_URL=https://login.microsoftonline.com/organizations/oauth2/v2.0/authorizeALEPH_OAUTH_TOKEN_URL=https://login.microsoftonline.com/common/oauth2/tokenALEPH_OAUTH_SCOPE=openid profile email user.readALEPH_OAUTH_TOKEN_METHOD=POST
Troubleshooting help can be found in the Technical FAQ.