Updated with latest changes from dev

Author: kzgrzendek

.github/workflows/ci-redcap-fastcgi-client.yaml

@@ -0,0 +1,18 @@
+{
+    "cSpell.words": [
+        "aphp",
+        "Dockle",
+        "edocs",
+        "ghostscript",
+        "imagick",
+        "libfcgi",
+        "logfile",
+        "maxbytes",
+        "mysqli",
+        "rpcinterface",
+        "shibd",
+        "stopasgroup",
+        "supervisord",
+        "usecase"
+    ]
+}

.vscode/settings.json

@@ -12,12 +12,12 @@ Those images are as follow :
 
 Each subfolder contains its own README file.
 
-All those containers are `rootless`, and **none of them is containing, or distributing REDCap binairies**. 
+All those containers are `rootless`, and **none of them is containing, or distributing REDCap binaries**. 
 If you wish to use REDCap and are not sure where to start, you may visit the dedicated [REDCap Community Site](https://projectredcap.org/resources/community/).
 
-## Continous Integration / Continous Delivery
+## continuous Integration / continuous Delivery
 
-This project uses 3 Github Workflows (presents under the .github/workflows directory), which will, for each image :
+This project uses two Github Workflows (presents under the .github/workflows directory), which will, for each image :
 - Lint the Dockerfile using `Hadolint`
 - Scan the container images using `Dockle`
 - Runs critical vulnerability, secrets and license checks on the container image using `Trivy`
@@ -29,6 +29,6 @@ You're welcome to read the [contribution guidelines](./CONTRIBUTING.md).
 
 ## How is this project licensed?
 
-The informations about the licensing and the dependencies of this project can be found under : 
+The information about the licensing and the dependencies of this project can be found under : 
 - The [project's license file](./LICENSE)
 - The [legal notice](./NOTICE)

README.md

@@ -1,18 +1,18 @@
 # `aphp/httpd-shibd` container image
 
 ## Description
-This image aims to build a custom container made to host an instance of Apache HTTPd and Shibboleth. Since Shibboleth is provided as a HTTPd module that spawns its own process, it cannot be easily isolated in a dedicated container. This container is then spawning and managing both of those processes with a `supervisord` rootless installation.
+This image aims to build a custom container made to host an instance of Apache HTTPd and Shibboleth. Since Shibboleth is provided as a HTTPd module that spawns its own process, it cannot be easily isolated in a dedicated container. This container is then spawning and managing both processes with a `supervisord` rootless installation.
 You can then map a `supervisord` configuration file that will handle the spawning of HTTPd and/or Shibboleth, according to your usecase.
 
 ## Content
-This image use [the reccomended way to install Shibboleth](https://shibboleth.atlassian.net/wiki/spaces/SP3/pages/2065335566/RPMInstall) on a RHEL/CentOS/RockyLinux 8+ base OS, alogside httpd.
-A dedicated non-root user is then created in order to manage the processes in a secure way.
+This image use [the recommended way to install Shibboleth](https://shibboleth.atlassian.net/wiki/spaces/SP3/pages/2065335566/RPMInstall) on a RHEL/CentOS/RockyLinux 8+ base OS, alongside httpd.
+A dedicated non-root user is also created in order to manage the processes in a secure way.
 
 ## Configuration
 
 ### supervisord
 
-Usually, a `supervisord` configuration file is used alongside this image, in order to efficienly manage and logs the processes activity.
+Usually, a `supervisord` configuration file is used alongside this image, in order to efficiently manage and logs the processes activity.
 
 Here's an example :
 
@@ -54,7 +54,7 @@ stdout_logfile_maxbytes=0
 
 ### HTTPd
 
-Depending of your usecase, the REDcap Communite Site can provide you with the best ways to configure your HTTPd server.
+Depending of your usecase, [the REDcap Community Site](https://projectredcap.org/resources/community/) can provide you with the best ways to configure your HTTPd server.
 
 ## How to use
 
@@ -64,7 +64,7 @@ The container image build from this project's Github Workflow is hosted on the G
 docker pull ghcr.io/aphp/redcap-httpd-shibd:latest
 ```
 
-If you wish to run it alongside the `supervisord` config file, juste use the following command : 
+If you wish to run it alongside the `supervisord` config file, just use the following command : 
 
 ```sh
 docker run ghcr.io/aphp/redcap-httpd-shibd:latest -v ${your-config-file}:/etc/supervisor/supervisord-redcap-front.conf

fastcgi-client/Dockerfile

@@ -6,9 +6,11 @@ RUN apt-get update -y &&\
     apt-get purge -y \
         wget &&\
     apt-get install -y --no-install-recommends \
+        default-mysql-client \
         libfcgi-bin \
         msmtp \
         libcurl4-openssl-dev \
+        ghostscript \
         libzip-dev \
         libfreetype6-dev \
         libjpeg62-turbo-dev \

fastcgi-client/README.md

@@ -1,20 +1,22 @@
 # `aphp/php-fpm` container image
 
 ## Description
-This image aims to provides with a PHP 8.2 FPM server, including all the dependencies that REDCap needs to operates correctly (this includes several image processing librairies, as well as some custom PHP extensions as `imagick`).
+This image aims to provides with a PHP 8.2 FPM server, including all the dependencies that REDCap needs to operates correctly (this includes several image processing libraries, as well as some custom PHP extensions as `imagick`).
 
-**This image doesn't contains, nor distributes REDCap binairies**. 
+**This image doesn't contains, nor distributes REDCap binaries**. 
 If you wish to use REDCap and are not sure where to start, you may visit the dedicated [REDCap Community Site](https://projectredcap.org/resources/community/).
 
 ## Content
-The image is based on the official PHP 8.2 FPM image (debian-bookworm flavor), on top of which are added a few librairies and php extensions, such as :
+The image is based on the official PHP 8.2 FPM image (debian-bookworm flavor), on top of which are added a few libraries and php extensions, such as :
 - `imagick`
 - `libpng`
 - `libcurl`
 - `mysqli`
 - `ghostscript`
+- `default-mysql-client` (used to setup REDCap DB by the startup probe used by APHP REDCap Helm Chart)
+- `libfcgi-bin` (used to launch REDCap cronjobs by the liveness probe probe used by APHP REDCap Helm Chart)
 
-On top of this, the `/app/redcap` (with a symlink pointing to`/var/www/redcap`) and `/edocs` dirs are created with suitable persmissions, ready to handle a REDCap installation.
+On top of this, the `/app/redcap` (with a symlink pointing to`/var/www/redcap`) and `/edocs` dirs are created with suitable permissions, ready to handle a REDCap installation.
 Finally, the image being rootless, the user `www-data` is exposed as the one executing the process. 
 
 ## How to use
@@ -25,7 +27,7 @@ The container image build from this project's Github Workflow is hosted on the G
 docker pull ghcr.io/aphp/redcap-php-fpm:latest
 ```
 
-If you want to serve the REDCap application with that image, you will have to retrieve the REDCap install archive, and map the content of the `redcap` directory to `` directory inside the container, like so (example with Docker) : 
+If you want to serve the REDCap application with that image, you will have to retrieve the REDCap install archive, and map the content of the `redcap` directory to the `/var/www/redcap` directory inside the container, like so (example with Docker) : 
 
 ```sh
 docker run ghcr.io/aphp/redcap-php-fpm:latest -v ${redcap-app-dir}:/var/www/redcap