Fix persistence documentation in Nami modules

Fix errors in:

-Run the application using Docker Compose
-Persisting your application
This commit is contained in:
raquel-campuzano
2016-11-17 16:40:14 +01:00
parent fef127bed6
commit 1725af8ac9

View File

@@ -75,13 +75,15 @@ 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 `prestashop_data` and `apache_data` volumes.
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.
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.
> **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
### Mount host directories as data volumes with Docker Compose
This requires a sightly modification from the template previously shown:
This requires a sightly modification from the `docker-compose.yml` template previously shown:
```yaml
version: '2'
@@ -92,30 +94,34 @@ services:
- '/path/to/your/local/mariadb_data:/bitnami/mariadb'
prestashop:
image: 'bitnami/prestashop:latest'
depends_on:
- mariadb
ports:
- '80:80'
- '443:443'
volumes:
- '/path/to/your/local/prestashop_data:/bitnami/prestashop'
- '/path/to/your/local/apache_data:/bitnami/apache'
depends_on:
- mariadb
- '/path/to/prestashop-persistence:/bitnami/prestashop'
- '/path/to/apache-persistence/bitnami/apache'
```
### Mount persistent folders manually
### Mount host directories as data volumes using the Docker command line
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:
1. Create a network (if it does not exist):
```
$ docker network create prestashop_network
$ docker network create prestashop
```
2. Start a MariaDB database in the previous network:
2. Create a MariaDB container with host volume:
```
$ 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=prestashop_network bitnami/mariadb
$ docker run -d --name mariadb \
--net prestashop \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
```
*Note:* You need to give the container a name in order to PrestaShop to resolve the host
@@ -123,7 +129,12 @@ In this case you need to specify the directories to mount on the run command. Th
3. Run the PrestaShop container:
```
$ docker run -d -p 80:80 --name prestashop -v /your/local/path/bitnami/prestashop:/bitnami/prestashop --network=prestashop_network bitnami/prestashop
$ docker run -d --name prestashop -p 80:80 -p 443:443 \
--net prestashop \
--volume /path/to/prestashop-persistence:/bitnami/prestashop \
--volume /path/to/apache-persistence:/bitnami/apache \
--volume /path/to/php-persistence:/bitnami/php \
bitnami/prestashop:latest
```
# Upgrade this application