From a586de0042a2c3b6fe67486017723faf81fa101e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Rodr=C3=ADguez=20Hern=C3=A1ndez?= Date: Tue, 20 Mar 2018 10:59:00 +0100 Subject: [PATCH] [stable/drupal] Fix some typos (#4231) * [stable/ghost] Fix some typos * [stable/drupal] Fix some typos * Revert "[stable/ghost] Fix some typos" This reverts commit fe3bc14a3ec611dc4f455a936128b2c771579c40. * Update README.md Another typo (replace tables by table) * Update Chart.yaml Bump version * Update README.md Implement @sameersbn suggestions --- stable/drupal/Chart.yaml | 2 +- stable/drupal/README.md | 17 +++++++++++++---- 2 files changed, 14 insertions(+), 5 deletions(-) diff --git a/stable/drupal/Chart.yaml b/stable/drupal/Chart.yaml index f3755e6e01..ae19d58efd 100644 --- a/stable/drupal/Chart.yaml +++ b/stable/drupal/Chart.yaml @@ -1,5 +1,5 @@ name: drupal -version: 0.11.11 +version: 0.11.12 appVersion: 8.5.0 description: One of the most versatile open source content management systems. keywords: diff --git a/stable/drupal/README.md b/stable/drupal/README.md index 09cc24fea6..a605104ded 100644 --- a/stable/drupal/README.md +++ b/stable/drupal/README.md @@ -43,7 +43,7 @@ The command removes all the Kubernetes components associated with the chart and ## Configuration -The following tables lists the configurable parameters of the Drupal chart and their default values. +The following table lists the configurable parameters of the Drupal chart and their default values. | Parameter | Description | Default | | --------------------------------- | ------------------------------------- | --------------------------------------------------------- | @@ -92,7 +92,7 @@ $ helm install --name my-release \ stable/drupal ``` -The above command sets the Drupal administrator account username and password to `admin` and `password` respectively. Additionally it sets the MariaDB `root` user password to `secretpassword`. +The above command sets the Drupal administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`. Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, @@ -112,16 +112,20 @@ If you configure the `image` value to one in a private registry, you will need t 1. Manually create image pull secret(s) in the namespace. See [this YAML example reference](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config). Consult your image registry's documentation about getting the appropriate secret. 1. Note that the `imagePullSecrets` configuration value cannot currently be passed to helm using the `--set` parameter, so you must supply these using a `values.yaml` file, such as: + ```yaml imagePullSecrets: - name: SECRET_NAME ``` + 1. Install the chart + ```console helm install --name my-release -f values.yaml stable/drupal ``` ## Persistence + The configured image must store Drupal data and Apache configurations in separate paths of the container. The [Bitnami Drupal](https://github.com/bitnami/bitnami-docker-drupal) image stores the Drupal data and Apache configurations at the `/bitnami/drupal` and `/bitnami/apache` paths of the container. If you wish to override the `image` value, and your image stores this data and configurations in different paths, you may specify these paths with `volumeMounts.drupal.mountPath` and `volumeMounts.apache.mountPath`. @@ -134,6 +138,7 @@ See the [Configuration](#configuration) section to configure the PVC or to disab 1. Create the PersistentVolume 1. Create the PersistentVolumeClaim 1. Install the chart + ```bash $ helm install --name my-release --set persistence.drupal.existingClaim=PVC_NAME stable/drupal ``` @@ -141,14 +146,18 @@ $ helm install --name my-release --set persistence.drupal.existingClaim=PVC_NAME ### Host path #### System compatibility + - The local filesystem accessibility to a container in a pod with `hostPath` has been tested on OSX/MacOS with xhyve, and Linux with VirtualBox. - Windows has not been tested with the supported VM drivers. Minikube does however officially support [Mounting Host Folders](https://github.com/kubernetes/minikube/blob/master/docs/host_folder_mount.md) per pod. Or you may manually sync your container whenever host files are changed with tools like [docker-sync](https://github.com/EugenMayer/docker-sync) or [docker-bg-sync](https://github.com/cweagans/docker-bg-sync). #### Mounting steps + 1. The specified `hostPath` directory must already exist (create one if it does not). 1. Install the chart + ```bash $ helm install --name my-release --set persistence.drupal.hostPath=/PATH/TO/HOST/MOUNT stable/drupal ``` - This will mount the `drupal-data` volume into the `hostPath` directory, if the site has not already been initialized. If it has, your host machine changes will persist. -1. Because the container can not control the host machine’s directory permissions, you must set the Drupal file directory permissions yourself and disable or clear Drupal cache. See Drupal Core’s [INSTALL.txt](http://cgit.drupalcode.org/drupal/tree/core/INSTALL.txt?h=8.3.x#n152) for setting file permissions, and see [Drupal handbook page](https://www.drupal.org/node/2598914) to disable cache, or [Drush handbook](https://drushcommands.com/drush-8x/cache/cache-rebuild/) to clear cache. + + This will mount the `drupal-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch. +1. Because the container cannot control the host machine’s directory permissions, you must set the Drupal file directory permissions yourself and disable or clear Drupal cache. See Drupal Core’s [INSTALL.txt](http://cgit.drupalcode.org/drupal/tree/core/INSTALL.txt?h=8.3.x#n152) for setting file permissions, and see [Drupal handbook page](https://www.drupal.org/node/2598914) to disable the cache, or [Drush handbook](https://drushcommands.com/drush-8x/cache/cache-rebuild/) to clear cache.