I am running Bonita in docker containers and using Kubernetes. Using Kubernetes or not it not that relevant but if you are using docker, the following is probably interesting for you. I used to run the migrations manually (ie sopping my container, mounting a volume with the config and migration scripts, restarting the container, running the tool, restarting a new container on the new version). While that works... it is not the simplest...
Ironically, the documentation on the Official Docker hub page mentions some wget, unzip, etc... All kind of stuff no one really want to do :)
Give a description to protect the serverAPI like the Tomcat Valve do.
By default, the servletAPI is open, and any host can connect to a BonitaServer, then use the BONITA JAVA API to do any operation.
This filter is able to protect the servletAPI, to describe which host can access the BONITA JAVA API
The filter verify that the RemoteAddr match the pattern. This is the same usage as the org.apache.catalina.valves.RequestFilterValve except that a filter can be setup for a specific URL, not all the tomcat
What's about this specific code insides diagrams and web-pages ? How do I know the level of quality of this code ? How can I detect potential misconception, code smell or bug ?
This is what Bonita Extract Sources provide you : A way to analyse code hidden in diagrams or web-pages