master:

develop:

tx-job-handler (part of tx platform)

This program accepts jobs from a rq/redis queue (placed there by the [tx-enqueue-job](https://github.com/unfoldingWord-dev/tx-enqueue-job)) program.

Setup

Requires Python 3.6 or later (Python2 compatibility has been removed.)

Satisfy basic dependencies:

git clone https://github.com/unfoldingWord-dev/tx-job-handler.git
OR/ with ssh: git clone git@github.com:unfoldingWord-dev/tx-job-handler.git
sudo apt-get install python3-pip

We recommend you create a Python virtual environment to help manage Python package dependencies:

cd tx-job-handler
python3 -m venv myVenv

Now load that virtual environment and install dependencies:

source myVenv/bin/activate
make dependencies

Deployment

Travis-CI is hooked to from GitHub to automatically test commits to both the develop and master branches, and on success, to build containers (tagged with those branch names) that are pushed to [DockerHub](https://hub.docker.com/u/unfoldingword/).

To fetch the container use something like:

docker pull --all-tags unfoldingword/tx_job_handler

or

docker pull unfoldingword/tx_job_handler:develop

To view downloaded images and their tags:

docker images

To test the container (assuming that the confidential environment variables are already set in the current environment) use:

docker run --env AWS_ACCESS_KEY_ID --env AWS_SECRET_ACCESS_KEY --env QUEUE_PREFIX=dev- --env DEBUG_MODE=True --env REDIS_URL="redis://<redis_hostname>:6379" --net="host" --name dev-tx_job_handler --rm unfoldingword/tx_job_handler:develop

or if not (and adding optional GRAPHITE_HOSTNAME):

docker run --env AWS_ACCESS_KEY_ID=<access_key> --env AWS_SECRET_ACCESS_KEY=<sa_key> --env QUEUE_PREFIX=dev- --env DEBUG_MODE=True GRAPHITE_HOSTNAME=<graphite_hostname> --env REDIS_URL="redis://<redis_hostname>:6379" --env --net="host" --name dev-tx_job_handler --rm unfoldingword/tx_job_handler:develop

NOTE: --rm automatically removes the container from the docker daemon when it exits

(it doesn't delete the pulled image from disk)

To run the container in production use with the desired values:

docker run --env AWS_ACCESS_KEY_ID=<access_key> --env AWS_SECRET_ACCESS_KEY=<sa_key> --env GRAPHITE_HOSTNAME=<graphite_hostname> --env REDIS_URL="redis://<redis_hostname>:6379" --net="host" --name tx_job_handler --detach --rm unfoldingword/tx_job_handler:master

Running containers can be viewed with (or append --all to see all containers):

docker ps

The output log can be viewed on the (AWS EC2) host machine at:

/var/lib/docker/containers/<containerID>/<containerID>-json.log

You can connect to a shell inside the container with commands like:

# Gives a shell on the running container -- Note: no bash shell available
docker exec -it `docker inspect --format="{{.Id}}" tx_job_handler` sh
docker exec -it `docker inspect --format="{{.Id}}" dev-tx_job_handler` sh

The container can be stopped with a command like:

docker stop dev-tx_job_handler

or using the full container name:

docker stop unfoldingword/tx_job_handler:develop

The production container will be deployed to the unfoldingWord AWS EC2 instance, where [Watchtower](https://github.com/v2tec/watchtower) will automatically check for, pull, and run updated containers.