88bee298da706e1f201cd33de416a9159ee83a92
jnavarr5
  Wed Feb 12 12:21:56 2025 -0800
Updating the documentation of which Linux distributions are supported for GBiC, refs #35034

diff --git src/product/installer/README.md src/product/installer/README.md
index 8ed99fdde2a..91ced6388ac 100644
--- src/product/installer/README.md
+++ src/product/installer/README.md
@@ -5,31 +5,32 @@
 The Genome Browser in the Cloud (GBiC) program is a convenient tool that automates the setup of a
 UCSC Genome Browser mirror. The GBiC program is for users who want to set up a full mirror of the 
 UCSC Genome Browser on their server/cloud instance, rather than using 
 [Genome Browser in a Box](gbib.html) (GBIB) 
 or our public website. Please see the 
 [Installation of a UCSC Genome Browser on a local machine (mirror)](mirror.html#considerations-before-installing-a-genome-browser)
 page for a summary of installation options, including the pros and cons of using a mirror
 installation via the GBiC program vs. using GBiB.
 
 The program works by setting up MySQL (MariaDB), Apache, and Ghostscript, and then copying the
 Genome Browser CGIs onto the machine under `/usr/local/apache/`. Because it also deactivates the
 default Apache htdocs/cgi folders, it is best run on a new machine, or at least a host that is not
 already used as a web server. The tool can also download full or partial assembly databases,
 update the Genome Browser CGIs, and remove temporary files (aka "trash cleaning").
 
-The GBiC program has been tested with Ubuntu 18/20 LTS, Centos 7.2/8, and Fedora 20.
+The GBiC program has been tested and confirmed to work with Ubuntu 18/20/22/24 LTS,
+Rocky 9.5, and Fedora 30/35/41.
 
 It has also been tested on virtual machines in Amazon EC2 (Centos) and Microsoft Azure (Ubuntu).
 
 If you want to load data on the fly from UCSC, you need to select the 
 data centers "US West (N. California)" (Amazon) or "West US" (Microsoft) for best performance. 
 Other data centers (e.g. East Coast) will require a local copy of the genome assembly, which 
 requires 2TB-7TB of storage for the hg19 assembly. Note that if you mirror multiple assemblies, this
 may in rare cases exceed 16TB, the current maximum size of a single Amazon EBS volume. In these
 cases, you may need to use RAID striping of multiple EBS volumes, or use Amazon EFS for the /gbdb
 files and Amazon Aurora for the MySQL tables. We have had one report from a user that the MySQL
 performance is better when served from Aurora instead of being served from the same EC2 instance;
 the cost may be higher in Aurora, depending on the type of usage.
 
 # Quick Start Instructions