diff --git a/bitnami/moodle/5.1/debian-12/Dockerfile b/bitnami/moodle/5.1/debian-12/Dockerfile index de23e64baa18..074670327365 100644 --- a/bitnami/moodle/5.1/debian-12/Dockerfile +++ b/bitnami/moodle/5.1/debian-12/Dockerfile @@ -9,7 +9,7 @@ ARG TARGETARCH ARG WITH_ALL_LOCALES="no" LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-02-18T12:41:45Z" \ + org.opencontainers.image.created="2026-03-02T17:16:37Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/moodle/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/moodle" \ @@ -24,18 +24,18 @@ ENV OS_ARCH="${TARGETARCH:-amd64}" \ COPY prebuildfs / SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"] # Install required system packages and dependencies -RUN install_packages acl ca-certificates cron curl libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libedit2 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpq5 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 locales openssl procps zlib1g +RUN install_packages acl ca-certificates cron curl libaudit1 libbrotli1 libbsd0 libbz2-1.0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libedit2 libexpat1 libffi8 libfftw3-double3 libfontconfig1 libfreetype6 libgcc-s1 libgcrypt20 libglib2.0-0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgssapi-krb5-2 libhashkit2 libhogweed6 libicu72 libidn2-0 libjpeg62-turbo libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.5-0 liblqr-1-0 libltdl7 liblzma5 libmagickcore-6.q16-6 libmagickwand-6.q16-6 libmd0 libmemcached11 libncurses6 libnettle8 libnghttp2-14 libonig5 libp11-kit0 libpam0g libpcre2-8-0 libpcre3 libpng16-16 libpsl5 libreadline8 librtmp1 libsasl2-2 libsodium23 libsqlite3-0 libssh2-1 libssl3 libstdc++6 libsybdb5 libtasn1-6 libtidy5deb1 libtinfo6 libunistring2 libuuid1 libwebp7 libx11-6 libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxslt1.1 libzip4 libzstd1 locales openssl procps zlib1g RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ "render-template-1.0.9-162-linux-${OS_ARCH}-debian-12" \ - "php-8.4.18-1-linux-${OS_ARCH}-debian-12" \ - "apache-2.4.66-0-linux-${OS_ARCH}-debian-12" \ - "postgresql-client-14.21.0-0-linux-${OS_ARCH}-debian-12" \ + "php-8.4.18-7-linux-${OS_ARCH}-debian-12" \ + "apache-2.4.66-1-linux-${OS_ARCH}-debian-12" \ + "postgresql-client-14.22.0-0-linux-${OS_ARCH}-debian-12" \ "mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \ - "libphp-8.4.18-0-linux-${OS_ARCH}-debian-12" \ - "moodle-5.1.3-0-linux-${OS_ARCH}-debian-12" \ + "libphp-8.4.18-5-linux-${OS_ARCH}-debian-12" \ + "moodle-5.1.3-1-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -67,9 +67,10 @@ ENV APACHE_HTTPS_PORT_NUMBER="" \ APACHE_HTTP_PORT_NUMBER="" \ APP_VERSION="5.1.3" \ BITNAMI_APP_NAME="moodle" \ - IMAGE_REVISION="3" \ + IMAGE_REVISION="4" \ LANG="en_US.UTF-8" \ LANGUAGE="en_US:en" \ + LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \ PATH="/opt/bitnami/common/bin:/opt/bitnami/php/bin:/opt/bitnami/php/sbin:/opt/bitnami/apache/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/mysql/bin:$PATH" EXPOSE 8080 8443 diff --git a/bitnami/moodle/README.md b/bitnami/moodle/README.md index 7f7598f57896..8eeb16841988 100644 --- a/bitnami/moodle/README.md +++ b/bitnami/moodle/README.md @@ -1,13 +1,11 @@ # Bitnami LMS powered by Moodle™ LMS -## What is Bitnami LMS powered by Moodle™ LMS? - > Moodle™ LMS is an open source online Learning Management System widely used at universities, schools, and corporations. It is modular and highly adaptable to any type of online learning. [Overview of Bitnami LMS powered by Moodle™ LMS](https://moodle.org/) Disclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide commercial license of any of these products. This listing has an open source license. Moodle(TM) LMS is run and maintained by Moodle HQ, that is a completely and separate project from Bitnami. -## TL;DR +## TL;DR ```console docker run --name moodle bitnami/moodle:latest @@ -15,7 +13,7 @@ docker run --name moodle bitnami/moodle:latest **Warning**: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Environment Variables](#environment-variables) section for a more secure deployment. -## Why use Bitnami Secure Images? +## Why use Bitnami Secure Images? Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images? @@ -32,15 +30,15 @@ Each image comes with valuable security metadata. You can view the metadata in [ If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy). -## How to deploy Moodle™ in Kubernetes? +## How to deploy Moodle™ in Kubernetes? Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Chart for Moodle™ GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/moodle). -## Supported tags and respective `Dockerfile` links +## Supported tags and respective `Dockerfile` links Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html). -## Get this image +## Get this image The recommended way to get the Bitnami Docker Image for Moodle™ is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/moodle). @@ -62,136 +60,25 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` -## How to use this image - -Moodle™ requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://github.com/bitnami/containers/tree/main/bitnami/mariadb) for the database requirements. - -### Using the Docker Command Line - -#### Step 1: Create a network - -```console -docker network create moodle-network -``` - -#### Step 2: Create a volume for MariaDB persistence and create a MariaDB container - -```console -$ docker volume create --name mariadb_data -docker run -d --name mariadb \ - --env ALLOW_EMPTY_PASSWORD=yes \ - --env MARIADB_USER=bn_moodle \ - --env MARIADB_PASSWORD=bitnami \ - --env MARIADB_DATABASE=bitnami_moodle \ - --network moodle-network \ - --volume mariadb_data:/bitnami/mariadb \ - bitnami/mariadb:latest -``` - -#### Step 3: Create volumes for Moodle™ persistence and launch the container - -```console -$ docker volume create --name moodle_data -docker run -d --name moodle \ - -p 8080:8080 -p 8443:8443 \ - --env ALLOW_EMPTY_PASSWORD=yes \ - --env MOODLE_DATABASE_USER=bn_moodle \ - --env MOODLE_DATABASE_PASSWORD=bitnami \ - --env MOODLE_DATABASE_NAME=bitnami_moodle \ - --network moodle-network \ - --volume moodle_data:/bitnami/moodle \ - --volume moodledata_data:/bitnami/moodledata \ - bitnami/moodle:latest -``` - -Access your application at `http://your-ip/` - -### Run the application using Docker Compose - -```console -curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/moodle/docker-compose.yml > docker-compose.yml -docker-compose up -d -``` +### Run the application using Docker Compose Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/moodle). -If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md). - -## Persisting your application +## Persisting your application If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. For persistence you should mount a directory at the `/bitnami/moodle` path and another at `/bitnami/moodledata`. If the mounted directory is empty, it will be initialized on the first run. Additionally you should mount a volume for persistence of the [MariaDB data](https://github.com/bitnami/containers/blob/main/bitnami/mariadb#persisting-your-database). -The above examples define the Docker volumes named mariadb_data, moodle_data and moodledata_data. The Moodle™ application state will persist as long as volumes are not removed. - To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data. -### Mount host directories as data volumes with Docker Compose +## Configuration -This requires a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository: +The following section describes the supported environment variables -```diff - mariadb: - ... - volumes: -- - mariadb_data:/bitnami/mariadb -+ - /path/to/mariadb-persistence:/bitnami/mariadb - ... - moodle: - ... - volumes: -- - moodle_data:/bitnami/moodle -+ - /path/to/moodle-persistence:/bitnami/moodle -- - moodledata_data:/bitnami/moodledata -+ - /path/to/moodledata-persistence:/bitnami/moodle - ... --volumes: -- mariadb_data: -- driver: local -- moodle_data: -- driver: local -``` +### Environment variables -### Mount host directories as data volumes using the Docker command line - -#### Step 1: Create a network (if it does not exist) - -```console -docker network create moodle-network -``` - -#### Step 2. Create a MariaDB container with host volume - -```console -docker run -d --name mariadb \ - --env ALLOW_EMPTY_PASSWORD=yes \ - --env MARIADB_USER=bn_moodle \ - --env MARIADB_PASSWORD=bitnami \ - --env MARIADB_DATABASE=bitnami_moodle \ - --network moodle-network \ - --volume /path/to/mariadb-persistence:/bitnami/mariadb \ - bitnami/mariadb:latest -``` - -#### Step 3. Create the Moodle™ container with host volumes - -```console -docker run -d --name moodle \ - -p 8080:8080 -p 8443:8443 \ - --env ALLOW_EMPTY_PASSWORD=yes \ - --env MOODLE_DATABASE_USER=bn_moodle \ - --env MOODLE_DATABASE_PASSWORD=bitnami \ - --env MOODLE_DATABASE_NAME=bitnami_moodle \ - --network moodle-network \ - --volume /path/to/moodle-persistence:/bitnami/moodle \ - --volume /path/to/moodledata-persistence:/bitnami/moodledata \ - bitnami/moodle:latest -``` - -## Configuration - -### Environment variables +The following tables list the main variables you can set. #### Customizable environment variables @@ -232,66 +119,15 @@ docker run -d --name moodle \ | `PHP_DEFAULT_MEMORY_LIMIT` | Default PHP memory limit. | `256M` | | `PHP_DEFAULT_MAX_INPUT_VARS` | Default maximum amount of input variables for PHP scripts. | `5000` | -When you start the Moodle™ image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. If you want to add a new environment variable: +When you start the Moodle™ image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. -- For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository: +### Examples -```yaml -moodle: - ... - environment: - - MOODLE_PASSWORD=my_password - ... -``` +#### SMTP configuration -- For manual execution add a `--env` option with each variable and value: +The `MOODLE_SMTP_*` environment variables allows you configure the SMTP settings in the application. Please take a look at the environment variables information above for more information. - ```console - docker run -d --name moodle -p 80:8080 -p 443:8443 \ - --env MOODLE_PASSWORD=my_password \ - --network moodle-tier \ - --volume /path/to/moodle-persistence:/bitnami/moodle \ - --volume /path/to/moodledata-persistence:/bitnami/moodledata \ - bitnami/moodle:latest - ``` - -### Examples - -This would be an example of SMTP configuration using a Gmail account: - -- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository: - - ```yaml - moodle: - ... - environment: - - MOODLE_DATABASE_USER=bn_moodle - - MOODLE_DATABASE_NAME=bitnami_moodle - - ALLOW_EMPTY_PASSWORD=yes - - MOODLE_SMTP_HOST=smtp.gmail.com - - MOODLE_SMTP_PORT=587 - - MOODLE_SMTP_USER=your_email@gmail.com - - MOODLE_SMTP_PASSWORD=your_password - - MOODLE_SMTP_PROTOCOL=tls - ... - ``` - -- For manual execution: - - ```console - docker run -d --name moodle -p 80:8080 -p 443:8443 \ - --env MOODLE_DATABASE_USER=bn_moodle \ - --env MOODLE_DATABASE_NAME=bitnami_moodle \ - --env MOODLE_SMTP_HOST=smtp.gmail.com \ - --env MOODLE_SMTP_PORT=587 \ - --env MOODLE_SMTP_USER=your_email@gmail.com \ - --env MOODLE_SMTP_PASSWORD=your_password \ - --env MOODLE_SMTP_PROTOCOL=tls \ - --network moodle-tier \ - --volume /path/to/moodle-persistence:/bitnami/moodle \ - --volume /path/to/moodledata-persistence:/bitnami/moodledata \ - bitnami/moodle:latest - ``` +#### Load balancer This would be an instance ready to be put behind the NGINX load balancer. @@ -320,7 +156,7 @@ This would be an instance ready to be put behind the NGINX load balancer. bitnami/moodle:latest ``` -### Installing additional language packs +### Installing additional language packs By default, this container packs a generic English version of Moodle™. Nevertheless, more Language Packs can be added to the default configuration using the in-platform Administration [interface](https://docs.moodle.org/38/en/Language_packs#Language_pack_installation_and_uninstallation). In order to fully support a new Language Pack it is also a requirement to update the system's locales files. To do that, you have several options: @@ -328,62 +164,10 @@ By default, this container packs a generic English version of Moodle™. Nev You can add extra locales using the `EXTRA_LOCALES` build-time variable when building the Docker image. The values must be separated by commas or semicolons (and optional spaces), and refer to entries in the `/usr/share/i18n/SUPPORTED` file inside the container. -For example, the following value would add French, German, Italian and Spanish, you would specify the following value in `EXTRA_LOCALES`: - -```text -fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8 -``` - -> NOTE: The locales `en_AU.UTF-8 UTF-8` and `en_US.UTF-8 UTF-8` will always be packaged, defaulting to `en_US.UTF-8 UTF-8`. - -To use `EXTRA_LOCALES`, you have two options: - -- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository: - - ```yaml - moodle: - ... - # image: bitnami/moodle:latest # remove this line ! - build: - context: . - dockerfile: Dockerfile - args: - - EXTRA_LOCALES=fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8 - ... - ``` - -- For manual execution, clone the repository and run the following command inside the `X/debian-12` directory: - - ```console - docker build -t bitnami/moodle:latest --build-arg EXTRA_LOCALES="fr_FR.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, es_ES.UTF-8 UTF-8" . - ``` - #### Enable all supported locales using the `WITH_ALL_LOCALES` build-time variable You can generate all supported locales by setting the build environment variable `WITH_ALL_LOCALES=yes`. Note that the generation of all the locales takes some time. -To use `WITH_ALL_LOCALES`, you have two options: - -- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository: - - ```yaml - moodle: - ... - # image: bitnami/moodle:latest # remove this line ! - build: - context: . - dockerfile: Dockerfile - args: - - WITH_ALL_LOCALES=yes - ... - ``` - -- For manual execution, clone the repository and run the following command inside the `X/debian-12` directory: - - ```console - docker build -t bitnami/moodle:latest --build-arg WITH_ALL_LOCALES=yes . - ``` - #### Extending the default image Finally, you can [extend](https://github.com/bitnami/containers/blob/main/bitnami/moodle#extend-this-image) the default image and adding as many locales as needed: @@ -395,13 +179,13 @@ RUN echo "es_ES.UTF-8 UTF-8" >> /etc/locale.gen && locale-gen Bear in mind that in the example above `es_ES.UTF-8 UTF-8` is the locale needed for the desired Language Pack to install. You may change this value to the locale corresponding to your pack. -### FIPS configuration in Bitnami Secure Images +### FIPS configuration in Bitnami Secure Images The Bitnami Bitnami LMS powered by Moodle™ LMS Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: - `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`. -## Logging +## Logging The Bitnami Docker image for Moodle™ sends the container logs to `stdout`. To view the logs: @@ -419,9 +203,9 @@ You can configure the containers [logging driver](https://docs.docker.com/engine By default, the logging of debug information is disabled. You can enable it by setting the environment variable `BITNAMI_DEBUG` to `true`. -## Maintenance +## Maintenance -### Backing up your container +### Backing up your container To backup your data, configuration and logs, follow these simple steps: @@ -446,7 +230,7 @@ docker run --rm -v /path/to/moodle-backups:/backups --volumes-from moodle busybo cp -a /bitnami/moodle /backups/latest ``` -### Restoring a backup +### Restoring a backup Restoring a backup is as simple as mounting the backup as volumes in the containers. @@ -472,52 +256,11 @@ For the Moodle™ container: bitnami/moodle:latest ``` -### Upgrade this image - -> **NOTE:** Since Moodle(TM) 3.4.0-r1, the application upgrades should be done manually inside the docker container following the [official documentation](https://docs.moodle.org/37/en/Upgrading). -> As an alternative, you can try upgrading using an updated Docker image. However, any data from the Moodle(TM) container will be lost and you will have to reinstall all the plugins and themes you manually added. - -Bitnami provides up-to-date versions of MariaDB and Moodle™, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Moodle™ container. For the MariaDB upgrade see: - -#### Step 1: Get the updated image - -```console -docker pull bitnami/moodle:latest -``` - -#### Step 2: Stop the running container - -Stop the currently running container using the command - -```console -docker-compose stop moodle -``` - -#### Step 3: Take a snapshot of the application state - -Follow the steps in [Backing up your container](#backing-up-your-container) to take a snapshot of the current application state. - -#### Step 4: Remove the currently running container - -Remove the currently running container by executing the following command: - -```console -docker-compose rm -v moodle -``` - -#### Step 5: Run the new image - -Update the image tag in `docker-compose.yml` and re-create your container with the new image: - -```console -docker-compose up -d -``` - -## Customize this image +## Customize this image The Bitnami Docker image for Moodle™ is designed to be extended so it can be used as the base image for your custom web applications. -### Extend this image +### Extend this image Before extending this image, please note there are certain configuration settings you can modify using the original image: @@ -530,7 +273,7 @@ If your desired customizations cannot be covered using the methods mentioned abo ```Dockerfile FROM bitnami/moodle -## Put your customizations below +## Put your customizations below ... ``` @@ -543,13 +286,13 @@ Here is an example of extending the image with the following modifications: ```Dockerfile FROM bitnami/moodle -## Install 'vim' +## Install 'vim' RUN install_packages vim -## Enable mod_ratelimit module +## Enable mod_ratelimit module RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf -## Modify the ports used by Apache by default +## Modify the ports used by Apache by default # It is also possible to change these environment variables at runtime ENV APACHE_HTTP_PORT_NUMBER=8181 ENV APACHE_HTTPS_PORT_NUMBER=8143 @@ -573,7 +316,7 @@ Based on the extended image, you can update the [`docker-compose.yml`](https://g ... ``` -## Notable Changes +## Notable Changes ## 3.9.0-debian-10-r17 @@ -594,7 +337,7 @@ Based on the extended image, you can update the [`docker-compose.yml`](https://g - The PHP configuration volume (`/bitnami/php`) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at `/opt/bitnami/php/conf`, or mount specific configuration files individually. - Enabling custom Apache certificates by placing them at `/opt/bitnami/apache/certs` has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at `/certs`. -## License +## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.