First commit

bitnami/moodle/Dockerfile

@@ -0,0 +1,26 @@
+FROM gcr.io/stacksmith-images/ubuntu:14.04-r8
+
+MAINTAINER Bitnami <containers@bitnami.com>
+
+ENV BITNAMI_APP_NAME=moodle \
+    BITNAMI_IMAGE_VERSION=3.1.0-r0 \
+    PATH=/opt/bitnami/php/bin:/opt/bitnami/mysql/bin/:$PATH
+
+# Additional modules required
+RUN bitnami-pkg unpack apache-2.4.20-0 --checksum ec415b0938e6df70327055c5be50f80b1307b785fa5bbd04c94a4077519e5dba
+RUN bitnami-pkg install mysql-client-10.1.13-2 --checksum d82ac222dfc58f460aaba05a70260940e8c55ff0b24e4e3ed72dec5f2bfb37fd
+RUN bitnami-pkg install php-5.6.23-0 --checksum 21f1d65e6f0721cbbad452ace681c5b1a41dec8aabe568140313dce045a0d537
+RUN bitnami-pkg install libphp-5.6.21-0 --checksum 8c1f994108eb17c69b00ac38617997b8ffad7a145a83848f38361b9571aeb73e
+
+# Install moodle
+RUN bitnami-pkg unpack moodle-3.1.0-0 --checksum 083af170464f7c8637319a34fba8254d7805d8179f7c9b391ca33a2a5be23a43
+
+COPY rootfs /
+
+VOLUME ["/bitnami/moodle", "/bitnami/apache"]
+
+EXPOSE 80 443
+
+ENTRYPOINT ["/app-entrypoint.sh"]
+
+CMD ["harpoon", "start", "--foreground", "apache"]

bitnami/moodle/LICENSE

@@ -0,0 +1,13 @@
+Copyright 2015 Bitnami
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

bitnami/moodle/README.md

@@ -0,0 +1,259 @@
+# What is Moodle?
+
+>Moodle is a very popular open source learning management solution (LMS) for the delivery of elearning courses and programs. It’s used not only by universities, but also by hundreds of corporations around the world who provide eLearning education for their employees. Moodle features a simple interface, drag-and-drop features, role-based permissions, deep reporting, many language translations, a well-documented API and more. With some of the biggest universities and organizations already using it, Moodle is ready to meet the needs of just about any size organization.
+
+https://www.moodle.org/
+
+# Prerequisites
+
+To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.
+
+# How to use this image
+
+## Run Moodle with a Database Container
+
+Running Moodle with a database server is the recommended way. You can either use docker-compose or run the containers manually.
+
+### Run the application using Docker Compose
+
+This is the recommended way to run Moodle. You can use the following docker compose template:
+
+```
+version: '2'
+
+services:
+  mariadb:
+    image: bitnami/mariadb:latest
+    volumes_from:
+      - mariadb_data
+
+  mariadb_data:
+    image: bitnami/mariadb:latest
+    entrypoint: 'true'
+
+  application:
+    build: bitnami/moodle:latest
+    ports:
+      - 80:80
+      - 443:443
+    volumes_from:
+      - application_data
+    depends_on:
+      - mariadb
+
+  application_data:
+    image: bitnami/moodle:latest
+    volumes:
+      - /bitnami/moodle
+      - /bitnami/apache
+    entrypoint: 'true'
+```
+
+### Run the application manually
+
+If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
+
+1. Create a new network for the application and the database:
+
+  ```
+  $ docker network create moodle_network
+  ```
+
+2. Start a MariaDB database in the network generated:
+
+  ```
+  $ docker run -d --name mariadb --net=moodle_network bitnami/mariadb
+  ```
+
+  *Note:* You need to give the container a name in order to Moodle to resolve the host
+
+3. Run the Moodle container:
+
+  ```
+  $ docker run -d -p 80:80 --name moodle --net=moodle_network bitnami/moodle
+  ```
+
+Then you can access your application at http://your-ip/
+
+## Persisting your application
+
+If you remove every container all your data will be lost, and the next time you run the image the application 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 are using docker-compose your data will be persistent as long as you don't remove `mariadb_data` and `application_data` containers. Those are data volume containers (See https://docs.docker.com/engine/userguide/containers/dockervolumes/ for more information). If you have run the containers manually or you want to mount the folders with persistent data in your host follow the next steps:
+
+> **Note!** If you have already started using your application, follow the steps on [backing](#backing-up-your-application) up to pull the data from your running container down to your host.
+
+### Mount persistent folders in the host using docker-compose
+
+This requires a sightly modification from the template previously shown:
+```
+version: '2'
+
+services:
+  mariadb:
+    image: bitnami/mariadb:latest
+    volumes_from:
+      - mariadb_data
+
+  mariadb_data:
+    image: bitnami/mariadb:latest
+    entrypoint: 'true'
+    volumes:
+      - /your/local/path/bitnami/mariadb/data:/bitnami/mariadb/data
+      - /your/local/path/bitnami/mariadb/conf:/bitnami/mariadb/conf
+
+  application:
+    image: bitnami/moodle:latest
+    ports:
+      - 80:80
+    volumes_from:
+      - application_data
+
+  application_data:
+    image: bitnami/moodle:latest
+    volumes:
+      - /bitnami/moodle
+      - /bitnami/apache
+    entrypoint: 'true'
+    mounts:
+      - /your/local/path/bitnami/moodle:/bitnami/moodle
+      - /your/local/path/bitnami/apache:/bitnami/apache
+```
+
+### Mount persistent folders manually
+
+In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:
+
+1. If you haven't done this before, create a new network for the application and the database:
+
+  ```
+  $ docker network create moodle_network
+  ```
+
+2. Start a MariaDB database in the previous network:
+
+  ```
+  $ docker run -d --name mariadb -v /your/local/path/bitnami/mariadb/data:/bitnami/mariadb/data -v /your/local/path/bitnami/mariadb/conf:/bitnami/mariadb/conf --network=moodle_network bitnami/mariadb
+  ```
+
+  *Note:* You need to give the container a name in order to Moodle to resolve the host
+
+3. Run the Moodle container:
+
+  ```
+  $ docker run -d -p 80:80 --name moodle -v /your/local/path/bitnami/moodle:/bitnami/moodle --network=moodle_network bitnami/moodle
+  ```
+
+# Upgrade this application
+
+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 https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image
+
+1. Get the updated images:
+
+```
+$ docker pull bitnami/moodle:latest
+```
+
+2. Stop your container
+
+ * For docker-compose: `$ docker-compose stop moodle`
+ * For manual execution: `$ docker stop moodle`
+
+3. (For non-compose execution only) Create a [backup](#backing-up-your-application) if you have not mounted the moodle folder in the host.
+
+4. Remove the currently running container
+
+ * For docker-compose: `$ docker-compose rm -v moodle`
+ * For manual execution: `$ docker rm -v moodle`
+
+5. Run the new image
+
+ * For docker-compose: `$ docker-compose start moodle`
+ * For manual execution ([mount](#mount-persistent-folders-manually) the directories if needed): `docker run --name moodle bitnami/moodle:latest`
+
+  *Note:* If you upgrade you will have to reinstall all the plugins and themes you manually added.
+
+
+# Configuration
+## Environment variables
+ 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:
+
+ * For docker-compose add the variable name and value under the application section:
+```
+application:
+  image: bitnami/moodle:latest
+  ports:
+    - 80:80
+  environment:
+    - MOODLE_PASSWORD=my_password
+  volumes_from:
+    - application_data
+```
+
+ * For manual execution add a `-e` option with each variable and value:
+
+```
+ $ docker run -d -e MOODLE_PASSWORD=my_password -p 80:80 --name moodle -v /your/local/path/bitnami/moodle:/bitnami/moodle --network=moodle_network bitnami/moodle
+```
+
+Available variables:
+
+ - `MOODLE_USERNAME`: Moodle application username. Default: **user**
+ - `MOODLE_PASSWORD`: Moodle application password. Default: **bitnami**
+ - `MOODLE_EMAIL`: Moodle application email. Default: **user@example.com**
+ - `MARIADB_USER`: Root user for the MariaDB database. Default: **root**
+ - `MARIADB_PASSWORD`: Root password for the MariaDB.
+ - `MARIADB_HOST`: Hostname for MariaDB server. Default: **mariadb**
+ - `MARIADB_PORT`: Port used by MariaDB server. Default: **3306**
+
+# Backing up your application
+
+To backup your application data follow these steps:
+
+1. Stop the running container:
+
+* For docker-compose: `$ docker-compose stop moodle`
+* For manual execution: `$ docker stop moodle`
+
+2. Copy the Moodle data folder in the host:
+
+```
+$ docker cp /your/local/path/bitnami:/bitnami/moodle
+```
+
+# Restoring a backup
+
+To restore your application using backed up data simply mount the folder with Moodle data in the container. See [persisting your application](#persisting-your-application) section for more info.
+
+# Contributing
+
+We'd love for you to contribute to this container. You can request new features by creating an
+[issue](https://github.com/bitnami/moodle/issues), or submit a
+[pull request](https://github.com/bitnami/moodle/pulls) with your contribution.
+
+# Issues
+
+If you encountered a problem running this container, you can file an
+[issue](https://github.com/bitnami/moodle/issues). For us to provide better support,
+be sure to include the following information in your issue:
+
+- Host OS and version
+- Docker version (`docker version`)
+- Output of `docker info`
+- Version of this container (`echo $BITNAMI_APP_VERSION` inside the container)
+- The command you used to run the container, and any relevant output you saw (masking any sensitive
+information)
+
+# License
+
+Copyright 2015 Bitnami
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

bitnami/moodle/docker-compose.yml

@@ -0,0 +1,23 @@
+version: '2'
+services:
+  mariadb:
+    image: 'bitnami/mariadb:latest'
+    volumes:
+      - 'mariadb_data:/bitnami/mariadb'
+  application:
+    image: 'bitnami/moodle:latest'
+    ports:
+      - '80:80'
+      - '443:443'
+    volumes:
+      - 'moodle_data:/bitnami/moodle'
+      - 'apache_data:/bitnami/apache'
+    depends_on:
+      - mariadb
+volumes:
+  mariadb_data:
+    driver: local
+  moodle_data:
+    driver: local
+  apache_data:
+    driver: local

bitnami/moodle/rootfs/app-entrypoint.sh

@@ -0,0 +1,36 @@
+#!/bin/bash
+set -e
+
+function initialize {
+    # Package can be "installed" or "unpacked"
+    status=`harpoon inspect $1`
+    if [[ "$status" == *'"lifecycle": "unpacked"'* ]]; then
+        # Clean up inputs
+        inputs=""
+        if [[ -f /$1-inputs.json ]]; then
+            inputs=--inputs-file=/$1-inputs.json
+        fi
+        harpoon initialize $1 $inputs
+    fi
+}
+
+# Set default values
+export MOODLE_USERNAME=${MOODLE_USERNAME:-"user"}
+export MOODLE_PASSWORD=${MOODLE_PASSWORD:-"bitnami"}
+export MOODLE_EMAIL=${MOODLE_EMAIL:-"user@example.com"}
+export MOODLE_LANGUAGE=${MOODLE_LANGUAGE:-"en"}
+export MARIADB_USER=${MARIADB_USER:-"root"}
+export MARIADB_HOST=${MARIADB_HOST:-"mariadb"}
+export MARIADB_PORT=${MARIADB_PORT:-"3306"}
+export MOODLE_SITENAME=${MOODLE_SITENAME:-"New Site"}
+
+
+
+if [[ "$1" == "harpoon" && "$2" == "start" ]] ||  [[ "$1" == "/init.sh" ]]; then
+   for module in apache moodle; do
+    initialize $module
+   done
+   echo "Starting application ..."
+fi
+
+exec /entrypoint.sh "$@"

bitnami/moodle/rootfs/moodle-inputs.json

@@ -0,0 +1,16 @@
+{
+  "username": "{{$global.env.MOODLE_USERNAME}}",
+  "password": "{{$global.env.MOODLE_PASSWORD}}",
+  "email": "{{$global.env.MOODLE_EMAIL}}",
+  "language": "{{$global.env.MOODLE_LANGUAGE}}",
+  "databaseAdminUser": "{{$global.env.MARIADB_USER}}",
+  "databaseAdminPassword": "{{$global.env.MARIADB_PASSWORD}}",
+  "databaseServerHost": "{{$global.env.MARIADB_HOST}}",
+  "databaseServerPort": "{{$global.env.MARIADB_PORT}}",
+  "smtpHost": "{{$global.env.SMTP_HOST}}",
+  "smtpPort": "{{$global.env.SMTP_PORT}}",
+  "smtpUser": "{{$global.env.SMTP_USER}}",
+  "smtpPassword": "{{$global.env.SMTP_PASSWORD}}",
+  "smtpProtocol": "{{$global.env.SMTP_PROTOCOL}}",
+  "moodleSiteName": "{{$global.env.MOODLE_SITENAME}}"
+}