From 26916468d3034033a6cc1a8dff9d8acd584b5695 Mon Sep 17 00:00:00 2001
From: Sebastiaan van Stijn <github@gone.nl>
Date: Tue, 22 Sep 2020 15:25:20 +0200
Subject: [PATCH] compose: add highlighting and automate version for
 compose-file

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
---
 compose/index.md | 38 +++++++++++++++++++++-----------------
 1 file changed, 21 insertions(+), 17 deletions(-)

diff --git a/compose/index.md b/compose/index.md
index 6db2e55d06..d36e4231e9 100644
--- a/compose/index.md
+++ b/compose/index.md
@@ -30,21 +30,23 @@ so they can be run together in an isolated environment.
 
 A `docker-compose.yml` looks like this:
 
-    version: '3'
-    services:
-      web:
-        build: .
-        ports:
-          - "5000:5000"
-        volumes:
-          - .:/code
-          - logvolume01:/var/log
-        links:
-          - redis
-      redis:
-        image: redis
+```yaml
+version: "{{ site.compose_file_v3 }}"
+services:
+  web:
+    build: .
+    ports:
+      - "5000:5000"
     volumes:
-      logvolume01: {}
+      - .:/code
+      - logvolume01:/var/log
+    links:
+      - redis
+  redis:
+    image: redis
+volumes:
+  logvolume01: {}
+```
 
 For more information about the Compose file, see the
 [Compose file reference](compose-file/index.md).
@@ -150,9 +152,11 @@ is the automated test suite. Automated end-to-end testing requires an
 environment in which to run tests. Compose provides a convenient way to create
 and destroy isolated testing environments for your test suite. By defining the full environment in a [Compose file](compose-file/index.md), you can create and destroy these environments in just a few commands:
 
-    $ docker-compose up -d
-    $ ./run_tests
-    $ docker-compose down
+```bash
+$ docker-compose up -d
+$ ./run_tests
+$ docker-compose down
+```
 
 ### Single host deployments