From daf9a192a91028abe1057ab37b25ed8d070e5ad1 Mon Sep 17 00:00:00 2001 From: Dan Smart Date: Tue, 6 Sep 2022 16:26:54 +0100 Subject: [PATCH] Fix typo --- docs/dev/docker-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dev/docker-setup.md b/docs/dev/docker-setup.md index 6113ddf2..5f24caf4 100644 --- a/docs/dev/docker-setup.md +++ b/docs/dev/docker-setup.md @@ -59,7 +59,7 @@ for development environments. * Use `docker-compose stop` to stop the container (without removing the volumes). -> Don't use `docker-compose down` to temporarily stop the container. If you do, the volumes will be removed, meaning that the contents of your DB will be be lost. After using `docker-compose stop`, continue to use `docker-compose up` to bring the container and volumes up as before, and the DB will still exist and work as expected. (See https://stackoverflow.com/questions/46428420/docker-compose-up-down-stop-start-difference and https://forums.docker.com/t/why-docker-compose-down-deletes-my-volume-how-to-define-volume-as-external/67433/11) +> Don't use `docker-compose down` to temporarily stop the container. If you do, the volumes will be removed, meaning that the contents of your DB will be lost. After using `docker-compose stop`, continue to use `docker-compose up` to bring the container and volumes up as before, and the DB will still exist and work as expected. (See https://stackoverflow.com/questions/46428420/docker-compose-up-down-stop-start-difference and https://forums.docker.com/t/why-docker-compose-down-deletes-my-volume-how-to-define-volume-as-external/67433/11) That's it! You should now be able to browse to `https://$PROJECT_NAME.local` (or whatever you set) and view the site. Note, at time of writing you will need to go through the install script to have WordPress set up.