From f1451ff502fbb06c062c0d983420afd368a3de00 Mon Sep 17 00:00:00 2001 From: raquel-campuzano Date: Fri, 18 Nov 2016 12:18:16 +0100 Subject: [PATCH] Fix minor typos, add clarification Clarification about volumes removal --- bitnami/prestashop/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/bitnami/prestashop/README.md b/bitnami/prestashop/README.md index 3ffe24b36288..4fd3b4c2fffe 100644 --- a/bitnami/prestashop/README.md +++ b/bitnami/prestashop/README.md @@ -79,11 +79,13 @@ If you remove every container all your data will be lost, and the next time you For persistence of the Prestashop deployment, the above examples define docker volumes namely `mariadb_data` and `prestashop_data` and `apache_data`. The Prestashop application state will persist as long as these volumes are not removed. +To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data. + > **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 host directories as data volumes with Docker Compose -This requires a sightly modification from the `docker-compose.yml` template previously shown: +This requires a minor change to the `docker-compose.yml` template previously shown: ```yaml version: '2'