5.9 release of TDS

Author: lesserwhirls

.org/readme.org

@@ -423,17 +423,17 @@ What to do when a version of the THREDDS data server is released?
 - Update the ~Dockerfile~ with the ~war~ file corresponding to the new version of the TDS. E.g.,
 
 #+begin_src shell
-  ENV THREDDS_WAR_URL https://downloads.unidata.ucar.edu/tds/5.8/thredds-5.8.war
+  ENV THREDDS_WAR_URL https://downloads.unidata.ucar.edu/tds/5.9/thredds-5.9.war
 #+end_src
 
 - Check with the netCDF group if versions of HDF5, zlib, and netCDF referenced in the ~Dockerfile~ need to be updated.
 - Update TDS versions in ~docker-compose.yml~ and ~docker-compose-swarm.yml~.
 - Update the ~CHANGELOG.md~ documenting updates to this project (not the TDS) since the last release.
-- Create a new git branch corresponding to this version of the TDS (e.g., ~5.8~).
+- Create a new git branch corresponding to this version of the TDS (e.g., ~5.9~).
 - Push the new branch out to the ~Unidata/thredds-docker~ GitHub repository. This branch will remain frozen in time going forward. Any subsequent updates to this project should happen on the the ~latest~ branch. The only exception to this convention is if there is a critical (e.g., security related) update that needs to be applied to the ~Dockerfile~ and associated files and eventually to the image (see below)
-- Build a docker image corresponding to the new version of the TDS (e.g., on the Docker build machine on Jetstream). E.g., ~docker build -t unidata/thredds-docker:5.8~.
+- Build a docker image corresponding to the new version of the TDS (e.g., on the Docker build machine on Jetstream). E.g., ~docker build -t unidata/thredds-docker:5.9~.
 - Test to ensure the image works.
-- Push it out DockerHub e.g., ~docker push unidata/thredds-docker:5.8~.
+- Push it out DockerHub e.g., ~docker push unidata/thredds-docker:5.9~.
 - Note that this image *does not* remain frozen in time for two reasons.
   1. It can get rebuilt time and again as upstream image updates need to be incorporated into this THREDDS image. It may be confusing for a versioned image to evolve, but it is the convention in Dockerland.
   2. It can get rebuilt in the rare case the Dockerfile or associated files are updated on the branch as mentioned earlier.

CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
+## [5.9] - 2025-07-13
+### Updated
+- 5.9 release of the Unidata TDS wrapped in a Docker container
+
 ## [5.8] - 2025-10-23
 ### Updated
 - 5.8 release of the Unidata TDS wrapped in a Docker container

Dockerfile

@@ -16,7 +16,7 @@ ENV HDF5_FILE=${HDF5_VER}.tar.gz
 ENV TDS_CONTENT_ROOT_PATH=/usr/local/tomcat/content
 ENV THREDDS_XMX_SIZE=4G
 ENV THREDDS_XMS_SIZE=4G
-ENV THREDDS_WAR_URL=https://downloads.unidata.ucar.edu/tds/5.8/thredds-5.8.war
+ENV THREDDS_WAR_URL=https://downloads.unidata.ucar.edu/tds/5.9/thredds-5.9.war
 
 COPY files/threddsConfig.xml ${CATALINA_HOME}/content/thredds/threddsConfig.xml
 COPY files/tomcat-users.xml ${CATALINA_HOME}/conf/tomcat-users.xml

README.md

@@ -419,17 +419,17 @@ What to do when a version of the THREDDS data server is released?
 -   Update the `Dockerfile` with the `war` file corresponding to the new version of the TDS. E.g.,
 
 ```shell
-ENV THREDDS_WAR_URL https://downloads.unidata.ucar.edu/tds/5.8/thredds-5.8.war
+ENV THREDDS_WAR_URL https://downloads.unidata.ucar.edu/tds/5.9/thredds-5.9.war
 ```
 
 -   Check with the netCDF group if versions of HDF5, zlib, and netCDF referenced in the `Dockerfile` need to be updated.
 -   Update TDS versions in `docker-compose.yml` and `docker-compose-swarm.yml`.
 -   Update the `CHANGELOG.md` documenting updates to this project (not the TDS) since the last release.
--   Create a new git branch corresponding to this version of the TDS (e.g., `5.8`).
+-   Create a new git branch corresponding to this version of the TDS (e.g., `5.9`).
 -   Push the new branch out to the `Unidata/thredds-docker` GitHub repository. This branch will remain frozen in time going forward. Any subsequent updates to this project should happen on the the `latest` branch. The only exception to this convention is if there is a critical (e.g., security related) update that needs to be applied to the `Dockerfile` and associated files and eventually to the image (see below)
--   Build a docker image corresponding to the new version of the TDS (e.g., on the Docker build machine on Jetstream). E.g., `docker build -t unidata/thredds-docker:5.8`.
+-   Build a docker image corresponding to the new version of the TDS (e.g., on the Docker build machine on Jetstream). E.g., `docker build -t unidata/thredds-docker:5.9`.
 -   Test to ensure the image works.
--   Push it out DockerHub e.g., `docker push unidata/thredds-docker:5.8`.
+-   Push it out DockerHub e.g., `docker push unidata/thredds-docker:5.9`.
 -   Note that this image **does not** remain frozen in time for two reasons.
     1.  It can get rebuilt time and again as upstream image updates need to be incorporated into this THREDDS image. It may be confusing for a versioned image to evolve, but it is the convention in Dockerland.
     2.  It can get rebuilt in the rare case the Dockerfile or associated files are updated on the branch as mentioned earlier.

docker-compose-swarm.yml

@@ -20,7 +20,7 @@ volumes:
 
 services:
   thredds:
-    image: unidata/thredds-docker:5.8
+    image: unidata/thredds-docker:5.9
     networks:
         thredds_network:
           aliases:

docker-compose.yml

@@ -2,14 +2,14 @@ version: '3'
 
 services:
   thredds-quickstart:
-    image: unidata/thredds-docker:5.8
+    image: unidata/thredds-docker:5.9
     ports:
       - "80:8080"
       - "443:8443"
       - "8443:8443"
 
   thredds-production:
-    image: unidata/thredds-docker:5.8
+    image: unidata/thredds-docker:5.9
     ports:
       - "80:8080"
       - "443:8443"