The previous statistics image (2.5-rc1) was replaced with a new version 2.5-rc2.
Version 2.5 is specified in the compose file and currently matches 2.5-rc2. The
streamline-emr image is also updated, now specifying version 2.5. For
consistency, the redis image is re-tagged with 2.5 as well, but the image itself
has not been changed.
The statistics image is updated to the latest available as of 2025-04-22, image
ID e0705e6cb218. This image was retagged with v2.5. The version is also updated
in the config file, now 2.5.
This helper script is used to build and install an 'app-only' version of the
package onto the local system. This is intendend to be used on the VM as a way
to quickly test new updates to the configuration files using images already
available on the system. This is MUCH faster than packaging with images.
The updated statistics image now pulls data from the database once per day, but
attempts to upload hourly to prevent large delays due to poor network
connectivity.
Previously, two volumes were bound to the statistics service. Both are removed
here. The first volume was a .env file, whose contents are now moved to the
compose file under the 'environment' keyword. The second, enabling persistent
storage for the /app folder, also caused the crucial 'fetch_and_update.php' to
be overwritten. Persistent storage is not currently necessary within this
service.
- Named volumes were still present (but unused) from a previous commit.
- A network was explicitly defined, but was not necessary as all services are
added to a default bridge network already.
- Remove host port mapping for redis container as the statistics service
accesses it directly (not through the host). This is also improves security.
This modified script replaces adds a wait condition on startup before attempting
to interact with the database. This is done with 'mariadb-admin ping' run in a
loop at 1s intervals, ultimately timing out after 30s if unsuccessful. Other
minor updates to the script print additional info the docker logs during
startup.
v2.0 was built using a demo database that should not have been present. v2.1
uses the same application, but should start with a clean database. This change
bumps the version to 2.1 and resets the database if the currently installed
version is 1.* or 2.0.
adminandGitLab Duo
alec.turner