Identity matching service

Locally:

/create_matching_record.sh 'A Name' DateOfBirth [format = YYYY-MM-DD] gender [M/F] 'Current address' 'Previous address'

For local development

SETTINGS='config.DevelopmentConfig'
DATABASE_URL='postgresql://localhost/matching'

Note in local dev port is assigned by dev env scripts

For production

PORT=[SOME NUMBER]
SETTINGS='config.Config'
DATABASE_URL='postgresql://user:password@db_host:port:db_name'

The machine that is being used to build this packages should have the following packages

• python
• pip
• virtualenv
• virtualenv-tools (sudo pip install virtualenv-tools)
• ruby
• fpm (sudo gem install fpm)

In base directory (where setup.py is)

python setup.py sdist

This creates a source distribution of the matching flask app in a subdirectory called dist. We'll install this into a virtualenv that will then be packaged into a deb.

cd packaging
./build.sh

This will create a virtualenv, install matching into that env. Then it will set virtualenv paths to match the eventual installation directory of the debian package that is the output of build.sh.

Note The packaging of a virtualenv using fpm may soon be much easier depending on outcome of this

The result of running ./build.sh is debian package will be created in packaging called matching_0.1_all.deb. The package has a basic upstart config, empty pre and post install and remove scripts. For the moment the installer is set to install to /opt/alpha/matching. Change as required. Also post install does not set ownership or permissions on the installed package.

Before installing in a production box you should:

• Set the environment variables as listed in environnment.sh (put the file into the package install dir)
• Create a no login user account that the matching service be owned and run as (at the moment in a dev vagrant it runs as root)

sudo dpkg -i matching_0.1_all.deb

Then run

sudo start matching

Note that this assumes you have set all the correct environment variables.

To uninstall

sudo dpkg -r matching

At the moment the migration version files and manage.py are included in packages and live in installation directory. I would for the moment run these after the install (and under control of configuration management tool) before running the service.

cd /opt/alpha/matching
python manage.py db upgrade