projects / discourse_docker.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a0958e4)
Fix upgrade instructions with a new container
authorBrendan Tobolaski <Brendan@Tobolaski.com>
Sun, 23 Mar 2014 02:50:06 +0000 (21:50 -0500)
committerBrendan Tobolaski <Brendan@Tobolaski.com>
Sun, 23 Mar 2014 02:50:06 +0000 (21:50 -0500)
If you attempt to bootstrap a new container without stopping or destroying the original it will fail because postgres will detect that it is running in another container.

README.md patch | blob | blame | history

diff --git a/README.md b/README.md
index f01957bcd2a063994e9494d83fd48450ea45d26e..de611ea659063311641b551fad7e8ad14b9c6f79 100644 (file)
--- a/README.md
+++ b/README.md
@@ -123,8 +123,8 @@ The Docker setup gives you multiple upgrade options:
 1. Use the front end at http://yoursite.com/admin/docker to upgrade an already running image.
 
 2. Create a new base image by running:
-  - `./launcher bootstrap my_image`
   - `./launcher destroy my_image`
+  - `./launcher bootstrap my_image`
   - `./launcher start my_image`
 
 ### Single Container vs. Multiple Container