Flowable docker in production


#1

With the help in https://forum.flowable.org/t/how-to-use-rest-api-in-docker/2977/9 I got my flowable microservice running without touching any java code. Here I’m looking for some advice to setup a reliable docker service.

I’m now using the all-in-one docker image

docker run -p 8080:8080 -d -e FLOWABLE_COMMON_APP_IDM-URL=http://192.168.1.9/flowable-idm -e SPRING_DATASOURCE_DRIVER-CLASS-NAME=org.postgresql.Driver -e SPRING_DATASOURCE_URL=jdbc:postgresql://192.168.1.9:5432/flowable -e SPRING_DATASOURCE_USERNAME=dbuser -e SPRING_DATASOURCE_PASSWORD=dbpasswd flowable/all-in-one

I want to setup flowable docker container stateless, I moved postgresql to host machine with the above command, how can I map storage volumns so attachments store at host machine?


#2

Hi.

That could be done by setting the property;

flowable.content.storage.root-folder

and mapping it.

docker run -p 8080:8080 -d 
-v /tmp/flowable-data:/data
-e FLOWABLE_CONTENT_STORAGE_ROOT-FOLDER=/data
-e FLOWABLE_COMMON_APP_IDM-URL=http://192.168.1.9/flowable-idm 
-e SPRING_DATASOURCE_DRIVER-CLASS-NAME=org.postgresql.Driver 
-e SPRING_DATASOURCE_URL=jdbc:postgresql://192.168.1.9:5432/flowable 
-e SPRING_DATASOURCE_USERNAME=dbuser 
-e SPRING_DATASOURCE_PASSWORD=dbpasswd
 flowable/all-in-one

By the way. You’re using the all-in-one image. Which is of course fine.
But if you want to deploy in a more true ‘microservice’ way you can use the separete images. This way each container has 1 responsibility.
Here are some example configurations: https://github.com/flowable/flowable-engine/tree/master/docker.

Hope this helps.

Regards,

Yvo


#3

You don’t need any java knowledge to get flowable running.
You just need to install tomcat and drop the war files into /tomcat/webapps.

Next step is to configure the ui-application.properties files to look at a database and done.


#4

I think that’s a use case (i.e., Terraform, Kubernetes, Docker, Microservices, Immutable Deployments, …) that a lot of developers would be interested in.

See:

And:

N.B. Camunda (like Flowable) is a fork of Activiti.


#5

Thanks for your post.
Note that Flowable is more of a continuation of Activiti than a fork. All the core developers have moved to Flowable and continuing the work that was started at Activiti. Activiti 7 is going in a completely different direction and can be considered more like a fork. Just my 2 cents.

Best regards,

Tijs