# Flowable docker in production

**URL:** <https://forum.flowable.org/t/flowable-docker-in-production/3041>\
**Category:** Uncategorized\
**Created:** [December 12, 2018, 12:47pm UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041 "2018-12-12T12:47:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xcaptain](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/xcaptain/32/1286_2.png) [@xcaptain](https://forum.flowable.org/u/xcaptain)\
**Post date:** [December 12, 2018, 12:47pm UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041/1 "2018-12-12T12:47:10Z")

</div>

With the help in [https://forum.flowable.org/t/how-to-use-rest-api-in-docker/2977/9](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

```auto
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?

---

<div class="post-metadata">

**Author:** ![yvo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/yvo/32/2231_2.png) [@yvo](https://forum.flowable.org/u/yvo)\
**Post date:** [December 12, 2018, 3:23pm UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041/2 "2018-12-12T15:23:19Z")

</div>

Hi.

That could be done by setting the property;

> flowable.content.storage.root-folder

and mapping it.

```auto
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: [flowable-engine/docker at main · flowable/flowable-engine · GitHub](https://github.com/flowable/flowable-engine/tree/master/docker).

Hope this helps.

Regards,

Yvo

---

<div class="post-metadata">

**Author:** ![Sebastiaan](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@Sebastiaan](https://forum.flowable.org/u/Sebastiaan)\
**Post date:** [December 12, 2018, 4:17pm UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041/3 "2018-12-12T16:17:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Robinyo](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Robinyo](https://forum.flowable.org/u/Robinyo)\
**Post date:** [December 12, 2018, 7:48pm UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041/4 "2018-12-12T19:48:20Z")

</div>

> [@xcaptain](#):
>
> I got my flowable microservice running without touching any java code

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:

- [https://robferguson.org/blog/2018/12/10/getting-started-with-flowable/](https://robferguson.org/blog/2018/12/10/getting-started-with-flowable/)

And:

- [Use Camunda as an easy-to-use REST-based orchestration and workflow engine (without touching Java) | by Bernd Rücker | berndruecker](https://blog.bernd-ruecker.com/use-camunda-without-touching-java-and-get-an-easy-to-use-rest-based-orchestration-and-workflow-7bdf25ac198e)
- [The Microservices Workflow Automation Cheat Sheet | by Bernd Rücker | berndruecker](https://blog.bernd-ruecker.com/the-microservice-workflow-automation-cheat-sheet-fc0a80dc25aa)
- [Architecture options to run a workflow engine | by Bernd Rücker | berndruecker](https://blog.bernd-ruecker.com/architecture-options-to-run-a-workflow-engine-6c2419902d91)

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

---

<div class="post-metadata">

**Author:** ![tijs](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tijs](https://forum.flowable.org/u/tijs)\
**Post date:** [December 13, 2018, 8:11am UTC](https://forum.flowable.org/t/flowable-docker-in-production/3041/5 "2018-12-13T08:11:19Z")

</div>

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