Currently, there exists a Dockerfile for imagemonkey-core (which is used by travis-ci for integration testing), but unfortunately this Dockerfile contains all the services in one docker container (which makes it pretty inflexible). We should split the ImageMonkey services up and create individual docker containers for
statworker
api
web
trendinglabels-worker
data-processor
blogsubscriptionworker
postgresql database
redis
If we structure the service (boundaries) properly, we should be able to use the dockerized approach also in production.
Currently, there exists a Dockerfile for imagemonkey-core (which is used by travis-ci for integration testing), but unfortunately this Dockerfile contains all the services in one docker container (which makes it pretty inflexible). We should split the ImageMonkey services up and create individual docker containers for
If we structure the service (boundaries) properly, we should be able to use the dockerized approach also in production.