...
You’ll have to tell the dashboard where its database lives, what the session cookie name is and, if you want to use session sync, the tomcat cluster. Currently you’ll always need to edit at least 1 XML configuration file.
Using containers
On For containers you can configure part of it them using environment variables but you’ll still need to edit one XML file for now.
...
You can use environment variables to configure where the database lives:
| Database host |
| Database port |
| Database username |
| Database password |
These can be specified as per the instructions on our Docker Deployments repository.
...
This should work on most cases, but if it doesn't suit your scenario see nginx's documentation about session persistence, or see the tomcat config below.
With tomcat (using synchronous session replication clustering)
Edit the tomcat’s server.xml on each of your nodes and add the following line under the <Engine> tag:
| Code Block | ||
|---|---|---|
| ||
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" /> |
This should enable clustering for tomcat.