cwoodcock-docker / activiti Goto Github PK

The README.me says that once the containers are deployed you can access the UI via:

http://<ip of docker host>:<container's 8080 port>/activiti-explorer

And the REST resources via:

http://<ip of docker host>:<container's 8080 port>/activiti-rest

I'm finding the Activiti Explorer UI is accessible at /activiti-explorer, but the REST endpoint is not available via /activiti-rest... I get:

I'm not all that familiar with the Java stack, but from looking at the Dockerfile and assets/ directory it looks like if one works then the other should too. Can you help me figure out what's wrong?

When restarting container it is most likely will change its IP address. This means, that previously generated /assets/config/db.properties file will stick with outdated connection settings forever. I would propose to have a temporal db setting file (copy of initial /assets/config/db.properties) to substitute and copy to destination dir:

# This performs variable substitution on the db.properties file then copies into both the REST and explorer apps
function update_db_properties() {
  cp /assets/config/db.properties /tmp/db.properties
  sed 's/{{JDBC_DRIVER_CLASS}}/'"${JDBC_DRIVER_CLASS}"'/g' -i /tmp/db.properties
  sed 's/{{JDBC_URL}}/'"${JDBC_URL}"'/g' -i /tmp/db.properties
  sed 's/{{JDBC_USER}}/'"${DB_USER}"'/g' -i /tmp/db.properties
  sed 's/{{JDBC_PASSWORD}}/'"${DB_PASS}"'/g' -i /tmp/db.properties
  sed 's/{{DB_TYPE}}/'"${DB_TYPE}"'/g' -i /tmp/db.properties
  cp -f /tmp/db.properties /opt/tomcat/webapps/activiti-rest/WEB-INF/classes
  cp -f /tmp/db.properties /opt/tomcat/webapps/activiti-explorer/WEB-INF/classes
  rm /tmp/db.properties
}

Should run as a normal user rather than as root.

@cwoodcock Is there a way to enable it for HTTPS so it can be put behind a LB that talks in https for the internal apache redirects?

I am not able to find a variable to do that, but I see the config of the apache active:

<!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
         This connector uses the NIO implementation that requires the JSSE
         style configuration. When using the APR/native implementation, the
         OpenSSL style configuration is required as described in the APR/native
         documentation -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
               maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->