Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-04 06:47:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

readme: cleanup whitespaces

Browse Source
This commit is contained in:
Sameer Naik
2016-11-23 17:35:56 +05:30
parent 2494f7fca8
commit adf9fd0cb9
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
bitnami/drupal/README.md
View File

@@ -84,7 +84,7 @@ Then you can access your application at http://your-ip/
## Persisting your application
If you remove every container and volume 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 remove every container and volume 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.
For persistence of the Drupal deployment, the above examples define docker volumes namely `mariadb_data`, `drupal_data` and `apache_data`. The Drupal application state will persist as long as these volumes are not removed.
@@ -113,7 +113,6 @@ services:
volumes:
- '/path/to/drupal-persistence:/bitnami/drupal'
- '/path/to/apache-persistence:/bitnami/apache'
```
### Mount host directories as data volumes using the Docker command line