Getting started

From Archivematica
Revision as of 16:27, 8 September 2015 by Hbecker (talk | contribs) (→‎Tests: Add section on running tests)
Jump to navigation Jump to search

Main Page > Development > Getting Started

This wiki page describes getting started with Archivematica as a developer. For user and administrative manuals, please see

Vital Stats


Archivematica consists of several projects working together.

  • Archivematica: Main repository containing the user-facing dashboard, task manager MCPServer and clients scripts for the MCPClient
  • Storage Service: Responsible for moving files to Archivematica for processing, and from Archivematica into storage
  • Format Policy Registry: Submodule shared between Archivematica and the Format Policy Registry (FPR) server that displays and updates FPR rules and commands

There are also several smaller repositories that support Archivematica in various ways. In general, you will not need these to develop on Archivematica.


There are two main ways to run Archivematica in development.

  1. Use ansible and vagrant to install Archivematica in a VM
  2. Install Archivematica on your development machine

Ansible & Vagrant

To install and run Archivematica from source on a VM:

  1. Checkout deployment repo
    • git clone
  2. Temporary: switch to playbooks/archivematica branch
    • git checkout playbooks/archivematica
  3. Install VirtualBox, Vagrant, Ansible
    • sudo apt-get install virtualbox vagrant
    • Vagrant must be at least 1.5
      • vagrant --version
    • sudo pip install ansible
  4. Helpers
  5. Create machine
    • cd deploy-pub/playbooks/archivematica/
    • vagrant up
    • Will prompt for sudo to modify /etc/hosts adding
  6. Login now available (but nothing needs to be run on the VM)
    • ssh
  7. Get updates to roles
    • ansible-galaxy install -r requirements.yml [--force]
  8. Execute playbook
    • ansible-playbook -i hosts singlenode.yml
  9. Archivematica should be available at and the storage service at

You may want to add this to your .ssh/config

Host 192.168.168.* *
  StrictHostKeyChecking no
  User root
  LogLevel ERROR

Development Machine

See development environment setup instructions


Archivematica and the related projects have a small but growing test suite. We use py.test to run our tests, which should be listed as a requirement in the development/local requirements file.

To run the tests, go to the repository root and run py.test

See below for project-specific setup or changes to running the tests.


Before running Archivematica tests, set the following environment variables.

set -xg DJANGO_SETTINGS_MODULE 'settings.local'
set -xg PYTHONPATH /usr/share/archivematica/dashboard/ /usr/lib/archivematica/archivematicaCommon/

export DJANGO_SETTINGS_MODULE='settings.local'
export PYTHONPATH=$PYTHONPATh:/usr/share/archivematica/dashboard/:/usr/lib/archivematica/archivematicaCommon/

Storage Service

Before running Storage Service tests, set the following environment variables

set -xg DJANGO_SETTINGS_MODULE storage_service.settings.local
set -xg SS_DB_NAME 'storage_service/default.db'
set -xg SS_DB_USER ''
set -xg SS_DB_PASSWORD ''
set -xg SS_DB_HOST ''
set -xg PYTHONPATH .  # The repository root

export DJANGO_SETTINGS_MODULE=storage_service.settings.local
export SS_DB_NAME='storage_service/default.db'
export SS_DB_USER=''
export SS_DB_PASSWORD=''
export SS_DB_HOST=''
export PYTHONPATH=.  # The repository root

Run tests from the storage_service subdirectory.

Skip known-failing test with py.test --ignore locations/tests/