From e9a827fed204e98019308bdb893114a013796c5f Mon Sep 17 00:00:00 2001
From: Professor Graham Leach <78756076+ProfessorGram@users.noreply.github.com>
Date: Fri, 27 Dec 2024 10:27:13 +0800
Subject: [PATCH] Small tweaks to the README.md top-to-bottom rewrite

updated example compose.yml with text of working file.  Fixed incorrect database reference in section regarding docker ps
---
 README.md | 35 +++++++++++++++++++----------------
 1 file changed, 19 insertions(+), 16 deletions(-)

diff --git a/README.md b/README.md
index dde0bdc..3ee101f 100644
--- a/README.md
+++ b/README.md
@@ -61,21 +61,24 @@ In this case we will create a directory named `backdrop-eval` to help assemble t
 In the `backdrop-eval` directory, create `compose.yml` file with the following contents:
 
 ```yaml
-backdrop:
-  image: backdrop/backdrop
-  links:
-    - db:mysql
-  ports:
-    - 8080:80
-
-db:
-  image: mysql
-  environment:
-    MYSQL_USER: backdrop
-    MYSQL_PASSWORD: backdrop
-    MYSQL_ALLOW_EMPTY_PASSWORD: 'yes'
-    MYSQL_DATABASE: backdrop
-
+services:
+  backdrop:
+    build:
+      context: ./1/apache
+    ports:
+      - 8088:80
+    environment:
+      BACKDROP_DB_HOST: db
+      BACKDROP_DB_USER: backdrop
+      BACKDROP_DB_PASSWORD: backdrop
+
+  db:
+    image: mysql
+    environment:
+      MYSQL_USER: backdrop
+      MYSQL_PASSWORD: backdrop
+      MYSQL_ALLOW_EMPTY_PASSWORD: 'yes'
+      MYSQL_DATABASE: backdrop
 ```
 
 ## Step 4:  Launch docker in such a way that it processes the startup file
@@ -113,7 +116,7 @@ Validating that backdrop indeed constructed a valid runtime environment may be a
 docker ps
 ```
 
-The resulting listing should include TWO (2) docker containers, one for the database server (mysql), one for the CMS (backdrop).
+The resulting listing should include TWO (2) docker containers, one for the database server (db), one for the CMS (backdrop).
 
 ## How to access the docker-based backdrop runtime environment
 Accessing the docker container may be accomplished with the following command: