A.P.P is a tool developed by Sydarkivera to create a user friendly and extensible interface for file processing workflows. The tools is developed with focus on handling every possible tool for verifying, validating and converting files in batches. To allow for great flexibility A.P.P has support for user defined tools which can easily be added to the system.

A.P.P is designed to be run in a docker environment. As such the whole system can be started with:

$ docker-compose -f docker-compose.prod.yml up --build

Setup the database. This is done by fisrt starting the server and ignoring the errors then running:

$ docker exec -it <container_name>_django_1 python manage.py migrate # example docker exec -it app-master_django_1 python manage.py migrate

$ docker exec -it <container_name>_django_1 python populate_database.py

You can find your container name by running "docker ps" and use the one that ends with "_django_1"

When this is done you can open the ui on localhost:80 by default. Sign in with admin:admin and go to "Global settings". You need to change the packages directory to "/code/packages" and you need to set the path to your workdir on your host (The absolute path of the workdir on docker host).

Finally, stop docker "docker-compose -f docker-compose.prod.yml stop" and start it again as you did before.

The folder /worker_container/images contains a set of images that can be run used to process files in the system as examples. Each docker instance should be based on worker_base to allow for per file status with low overhead. More details can be found under "Tool types"

For development the docker-compose file dev.yml is recommended. It can be started with:

$ docker-compose -f docker-compose.dev.yml up --build

Alternatively to build all containers and the smart docker containers the helper sh file "reset_for_development.sh" van be used. WARNING: This script will terminate and remove all running containers on the system. Don't use in production!!!

A simple command to be run in the Django docker container. Only suitable for simple commands.

The option to run a python script in the Django docker container. Only suitable for simple commands.

A docker container that will be started with one command and then exits. Useful for operations that can be run on all files in a package at once.

A docker alternative which must be based on "worker_base". This container will be started once per job and then run it's command per file with minimal overhead. This will likely be the most useful alternative. Examples of Smart docker containers can be found under worker_container/images

Contact simon@axenu.com or simon.nilsson@sydarkivera.se

This project is licensed under the terms of the GNU (General Public License)