Camunda Run at Operaton

Hello,
I would like to find out whether we should continue to pursue the former Camunda Run project at Operaton or whether there is little need for it.

I’m asking because I’m currently preparing the documentation for Operaton and stumbled across the ‘Run’ project.

What do you think? Do you use it, do you see a need for it or are there perhaps even completely different ideas/thoughts with a similar approach?

I like the concept of Camunda Run providing a kickstart option for easily getting started with the software. However, I believe that in today’s tech landscape, this should be fully containerized. Including some Docker Compose examples would be ideal—especially for setups involving external databases and other integrations.

3 Likes

Camunda Run was my entry ticket to the camunda platform. There should be a way to use Operaton as an external engine without much fuss. I concur with Julian. We should provide an easy to use containerized version to just run Operaton as an external engine. Docker Compose examples are nice to have in my opinion.

I’d like to propose a simple operaton docker container without any external dependencies as a first step towards a new “Operaton Quickstart” solution based on docker.

I completely agree with Julian. The easiest way is to describe a Docker run in the documentation and provide a ready-made compose file.

2 Likes

In the last years, I did a lot of Camunda 7 trainings for developers, sometimes Business Analysts also participated. The number of people who were not allowed to install / run Docker on their work machines or were not allowed to execute “external” Images there was surprisingly high. Running JARs from a downloaded ZIP was fine in the most cases, however :smiley:

(I think downloaded ZIP files are often retrieved and shared by a centralized instande, and are distributed more easly)

1 Like