Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-04-02 15:27:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix minor typos

Browse Source
This commit is contained in:
raquel-campuzano
2016-11-18 12:19:01 +01:00
parent 5d10b8fb20
commit e47e17cf66
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bitnami/suitecrm/README.md
View File

@@ -84,13 +84,13 @@ If you remove every container and volume all your data will be lost, and the nex
For persistence of the SuiteCRM deployment, the above examples define docker volumes namely `mariadb_data`, `suitecrm_data`, `apache_data` and `php_data`. The SuiteCRM application state will persist as long as these volumes are not removed.
If 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.
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:
```
version: '2'