This is documented as of release 1.1.1.2d

We chose the Apache Tomcat as a web application server for Score (formerly, SRT), because it is an open-source project under the Apache License 2.0 license and is stable for typical web applications. Although Score can be deployed on any servers which support the Java Servlet Container technology such as Glassfish, JBoss, Oracle WebLogic, we have no plans to provide any preferences or configurations for that. In spite of the fact that the latest release of the Apache Tomcat is 9, we have been using the Tomcat 8 release for maintaining stability.

We chose the MySQL relational database management system (RDBMS) as a data persistence facility for Score. While it is possible to make Score compatible with multiple RDBMS; more resources are required to maintain configuration files and database update scripts. In spite of the fact that the latest release of the MySQL is 8, we have been using the MySQL 5.7 release for maintaining stability.

• MySQL Workbench

Users can deploy SRT on the local machine using either a standalone deployment by a WAR packaging file or containerization by Docker containers. The following describes these two options.

• JDK 1.8.x.x.x The below configuration has been shown to support at least a couple of concurrent users without distributed installations of the database and the application.
• (v) CPU = 2 min cores, 4 recommended
• Memory = 16G
• Disk = 2G (the DB is tiny, most is OS and code dependencies)

The below configuration has been shown to support at least a couple of concurrent users without distributed installations of the database and the application.

• (v) CPU = 2 min cores, 4 recommended
• Memory = 16G
• Disk = 2G (the DB is tiny, most is OS and code dependencies)
• OS= RedHat (supported), or CentOS (unsupported RedHat)
• Docker (latest and greatest)

See here.