public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-21 11:43:09 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/moodle] Release 3.11.8-debian-11-r10 (#1038)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2022-07-28 14:57:46 +00:00
committed by GitHub
parent e15edaa469
commit fcdb83b75f
2 changed files with 28 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/moodle/3/debian-11/rootfs/opt/bitnami/scripts/apache/setup.sh
+2 -2
View File
@@ -27,7 +27,7 @@ fi
# Mount certificate files # Mount certificate files
if ! is_dir_empty "${APACHE_BASE_DIR}/certs"; then if ! is_dir_empty "${APACHE_BASE_DIR}/certs"; then
warn "The directory '${APACHE_BASE_DIR}/certs' was externally mounted. This is a legacy configuration and will be deprecated soon. Please mount certificate files at '/certs' instead. Find an example at: https://github.com/bitnami/bitnami-docker-apache#using-custom-ssl-certificates" warn "The directory '${APACHE_BASE_DIR}/certs' was externally mounted. This is a legacy configuration and will be deprecated soon. Please mount certificate files at '/certs' instead. Find an example at: https://github.com/bitnami/containers/tree/main/bitnami/apache#using-custom-ssl-certificates"
warn "Restoring certificates at '${APACHE_BASE_DIR}/certs' to '${APACHE_CONF_DIR}/bitnami/certs'" warn "Restoring certificates at '${APACHE_BASE_DIR}/certs' to '${APACHE_CONF_DIR}/bitnami/certs'"
rm -rf "${APACHE_CONF_DIR}/bitnami/certs" rm -rf "${APACHE_CONF_DIR}/bitnami/certs"
ln -sf "${APACHE_BASE_DIR}/certs" "${APACHE_CONF_DIR}/bitnami/certs" ln -sf "${APACHE_BASE_DIR}/certs" "${APACHE_CONF_DIR}/bitnami/certs"
@@ -46,7 +46,7 @@ fi
# Restore persisted configuration files (deprecated) # Restore persisted configuration files (deprecated)
if ! is_dir_empty "/bitnami/apache/conf"; then if ! is_dir_empty "/bitnami/apache/conf"; then
warn "The directory '/bitnami/apache/conf' was externally mounted. This is a legacy configuration and will be deprecated soon. Please mount certificate files at '${APACHE_CONF_DIR}' instead. Find an example at: https://github.com/bitnami/bitnami-docker-apache#full-configuration" warn "The directory '/bitnami/apache/conf' was externally mounted. This is a legacy configuration and will be deprecated soon. Please mount certificate files at '${APACHE_CONF_DIR}' instead. Find an example at: https://github.com/bitnami/containers/tree/main/bitnami/apache#full-configuration"
warn "Restoring configuration at '/bitnami/apache/conf' to '${APACHE_CONF_DIR}'" warn "Restoring configuration at '/bitnami/apache/conf' to '${APACHE_CONF_DIR}'"
rm -rf "$APACHE_CONF_DIR" rm -rf "$APACHE_CONF_DIR"
ln -sf "/bitnami/apache/conf" "$APACHE_CONF_DIR" ln -sf "/bitnami/apache/conf" "$APACHE_CONF_DIR"
bitnami/moodle/README.md
+26 -30
View File
@@ -11,7 +11,7 @@ Disclaimer: The respective trademarks mentioned in the offering are owned by the
## TL;DR ## TL;DR
```console ```console
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-moodle/master/docker-compose.yml > docker-compose.yml $ curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/moodle/docker-compose.yml > docker-compose.yml
$ docker-compose up -d $ docker-compose up -d
``` ```
@@ -37,10 +37,10 @@ Bitnami containers can be used with [Kubeapps](https://kubeapps.dev/) for deploy
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/). Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
* [`4`, `4-debian-11`, `4.0.2`, `4.0.2-debian-11-r5`, `latest` (4/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-moodle/blob/4.0.2-debian-11-r5/4/debian-11/Dockerfile) * [`4`, `4-debian-11`, `4.0.2`, `4.0.2-debian-11-r5`, `latest` (4/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/moodle/4/debian-11/Dockerfile)
* [`3`, `3-debian-11`, `3.11.8`, `3.11.8-debian-11-r9` (3/debian-11/Dockerfile)](https://github.com/bitnami/bitnami-docker-moodle/blob/3.11.8-debian-11-r9/3/debian-11/Dockerfile) * [`3`, `3-debian-11`, `3.11.8`, `3.11.8-debian-11-r10` (3/debian-11/Dockerfile)](https://github.com/bitnami/containers/blob/main/bitnami/moodle/3/debian-11/Dockerfile)
Subscribe to project updates by watching the [bitnami/moodle GitHub repo](https://github.com/bitnami/bitnami-docker-moodle). Subscribe to project updates by watching the [bitnami/containers GitHub repo](https://github.com/bitnami/containers).
## Get this image ## Get this image
@@ -56,22 +56,24 @@ To use a specific version, you can pull a versioned tag. You can view the [list
$ docker pull bitnami/moodle:[TAG] $ docker pull bitnami/moodle:[TAG]
``` ```
If you wish, you can also build the image yourself. If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.
```console ```console
$ docker build -t bitnami/moodle:latest 'https://github.com/bitnami/bitnami-docker-moodle.git#master:4/debian-11' $ git clone https://github.com/bitnami/containers.git
$ cd bitnami/APP/VERSION/OPERATING-SYSTEM
$ docker build -t bitnami/APP:latest .
``` ```
## How to use this image ## How to use this image
Moodle&trade; requires access to a MySQL or MariaDB database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://www.github.com/bitnami/bitnami-docker-mariadb) for the database requirements. Moodle&trade; 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.
### Run the application using Docker Compose ### Run the application using Docker Compose
The main folder of this repository contains a functional [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file. Run the application using it as shown below: The main folder of this repository contains a functional [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file. Run the application using it as shown below:
```console ```console
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-moodle/master/docker-compose.yml > docker-compose.yml $ curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/moodle/docker-compose.yml > docker-compose.yml
$ docker-compose up -d $ docker-compose up -d
``` ```
@@ -120,7 +122,7 @@ Access your application at `http://your-ip/`
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. 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. 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/bitnami-docker-mariadb#persisting-your-database). For persistence you should mount a directory at the `/bitnami/moodle` path. 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 and moodle_data. The Moodle&trade; application state will persist as long as volumes are not removed. The above examples define the Docker volumes named mariadb_data and moodle_data. The Moodle&trade; application state will persist as long as volumes are not removed.
@@ -128,7 +130,7 @@ To avoid inadvertent removal of volumes, you can mount host directories as data
### Mount host directories as data volumes with Docker Compose ### Mount host directories as data volumes with Docker Compose
This requires a minor change to the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: 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:
```diff ```diff
mariadb: mariadb:
@@ -191,7 +193,7 @@ $ docker run -d --name moodle \
When you start the Moodle&trade; 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&trade; 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:
* For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: * 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:
```yaml ```yaml
moodle: moodle:
@@ -292,7 +294,7 @@ To configure Moodle&trade; to send email using SMTP you can set the following en
This would be an example of SMTP configuration using a Gmail account: This would be an example of SMTP configuration using a Gmail account:
* Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: * Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository:
```yaml ```yaml
moodle: moodle:
@@ -327,7 +329,7 @@ This would be an example of SMTP configuration using a Gmail account:
This would be an instance ready to be put behind the NGINX load balancer. This would be an instance ready to be put behind the NGINX load balancer.
* Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: * Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository:
```yaml ```yaml
moodle: moodle:
@@ -367,7 +369,7 @@ For example, the following value would add French, German, Italian and Spanish,
To use `EXTRA_LOCALES`, you have two options: To use `EXTRA_LOCALES`, you have two options:
* Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: * Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository:
```yaml ```yaml
moodle: moodle:
@@ -393,7 +395,7 @@ You can generate all supported locales by setting the build environment variable
To use `WITH_ALL_LOCALES`, you have two options: To use `WITH_ALL_LOCALES`, you have two options:
* Modify the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository: * Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository:
```yaml ```yaml
moodle: moodle:
@@ -415,7 +417,7 @@ To use `WITH_ALL_LOCALES`, you have two options:
#### Extending the default image #### Extending the default image
Finally, you can [extend](https://github.com/bitnami/bitnami-docker-moodle#extend-this-image) the default image and adding as many locales as needed: 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:
```Dockerfile ```Dockerfile
FROM bitnami/moodle FROM bitnami/moodle
@@ -496,7 +498,7 @@ For the Moodle&trade; container:
> **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). > **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. > 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&trade;, 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&trade; container. For the MariaDB upgrade see: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image Bitnami provides up-to-date versions of MariaDB and Moodle&trade;, 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&trade; container. For the MariaDB upgrade see: https://github.com/bitnami/containers/tree/main/bitnami/mariadb#upgrade-this-image
#### Step 1: Get the updated image #### Step 1: Get the updated image
@@ -541,9 +543,9 @@ The Bitnami Docker image for Moodle&trade; is designed to be extended so it can
Before extending this image, please note there are certain configuration settings you can modify using the original image: Before extending this image, please note there are certain configuration settings you can modify using the original image:
- Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables `APACHE_HTTP_PORT_NUMBER` and `APACHE_HTTPS_PORT_NUMBER` respectively. - Settings that can be adapted using environment variables. For instance, you can change the ports used by Apache for HTTP and HTTPS, by setting the environment variables `APACHE_HTTP_PORT_NUMBER` and `APACHE_HTTPS_PORT_NUMBER` respectively.
- [Adding custom virtual hosts](https://github.com/bitnami/bitnami-docker-apache#adding-custom-virtual-hosts). - [Adding custom virtual hosts](https://github.com/bitnami/containers/blob/main/bitnami/apache#adding-custom-virtual-hosts).
- [Replacing the 'httpd.conf' file](https://github.com/bitnami/bitnami-docker-apache#full-configuration). - [Replacing the 'httpd.conf' file](https://github.com/bitnami/containers/blob/main/bitnami/apache#full-configuration).
- [Using custom SSL certificates](https://github.com/bitnami/bitnami-docker-apache#using-custom-ssl-certificates). - [Using custom SSL certificates](https://github.com/bitnami/containers/blob/main/bitnami/apache#using-custom-ssl-certificates).
If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below: If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:
@@ -575,7 +577,7 @@ ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143 EXPOSE 8181 8143
``` ```
Based on the extended image, you can update the [`docker-compose.yml`](https://github.com/bitnami/bitnami-docker-moodle/blob/master/docker-compose.yml) file present in this repository to add other features: Based on the extended image, you can update the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/moodle/docker-compose.yml) file present in this repository to add other features:
```diff ```diff
moodle: moodle:
@@ -615,17 +617,11 @@ Based on the extended image, you can update the [`docker-compose.yml`](https://g
## Contributing ## Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-moodle/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-moodle/pulls) with your contribution. We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues), or submit a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.
## Issues ## Issues
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-moodle/issues/new). Be sure to include the following information in your issue: If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/containers/issues/new/choose). For us to provide better support, be sure to fill the issue template.
- Host OS and version
- Docker version (`docker version`)
- Output of `docker info`
- Version of this container
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
### Community supported solution ### Community supported solution