Paylogic Deployment Tool

Paylogic Deployment Tool manages paylogic migrations, deployments and releases.

If you want to use it, please read the documentation below. Documentation Status

REST API client

There is a command line REST API client implemented as a separate project, see pdt-client

Development Environment

To set up the development environment, run:

# install system dependencies, requires sudo access!
make dependencies

# install python dependencies, initialize configs
make develop

Then, to run the django development server:

.env/bin/python runserver

Open a browser, go to and you can use the PDT.

Production Deployment

Automatic way - debian package

make deb [index_url=<local pypi index>]

This command will create debian package (located in ./build/pdt_<version from ./VERSION>.deb) with the application. Important file locations:

Default configuration which you need to adjust
PDT circus supervisor configuration (you shouldn’t need to change this)
Upstart configuration for PDT circus supervisor (you shouldn’t need to change this)
Default PDT sqlite3 database location (this is only the case if the database backend is sqlite3)
PDT code location

Manual way - build folder

make build [index_url=<local pypi index>]

This command will make ./build folder containing all needed to run the application.

The preferred method to deploy Django applications is to use WSGI supporting web server. Use build/ file as WSGI script.

There is one important thing to remember. Django serves media (static) files only in development mode. For running PDT in a production environment, you need to setup your web-server to serve the /static/ alias directly from the ./build/static folder.

Here is the tutorial for deployment with uwsgi

Make sure that production server has system packages mentioned in DEPENDENCIES file are installed (ubuntu 14.04).

After the deployment of the build folder to the production server:

cd <build folder>
# apply database migrations
PYTHONPATH=. django/bin/ syncdb

Using wheels

To speedup the build process, 2 make targets are implemented:

make wheel
Build wheels for all python dependencies, storing them in the cache directory
make upload-wheel (depends on make wheel)

Upload previously generated wheels to given private devpi server.


  • devpi_url - devpi server URL to use
  • devpi_path - index path to upload to
  • devpi_login - login to use for devpi authorization
  • devpi_password - password to use for devpi authorization

After you’ll upload wheels, make build and make develop time will be dramatically reduced, if you will pass index_url parameter pointing to the same devpi server index you used for make upload-wheel, for example:

make build index_url=

Be aware that binary wheels can only be used on exactly same architecture and environment as they were built.


For secret configuration, the nice YamJam is used.

Secret settings are loaded from 2 places:

place the production secrets there
<pdt root>/config.yaml
place the local development secrets there

Example of the configuration

    django_secret_key: my-secret-key-value
        engine: django.db.backends.sqlite3
        name: db.sqlite3
        dsn: # http://some-raven-dsn
        token: some-api-token
        token: some-fogbugz-token
        ci_project_field_id: cixproject
        migration_url_field_id: dbxmigration
        revision_field_id: revision
    hostname: localhost
    debug: true
        broker_url: redis://localhost:6379/0
        result_backend: redis://localhost:6379/0
        scheduler_url: redis://localhost:6379/1
            host: localhost
            port: 6379
            db: 3


This software is licensed under the MIT license

© 2015 Paylogic International.

Internal API


  • initial public release.