From fee520c3f4b36b6a23367880403d9940ab055bc5 Mon Sep 17 00:00:00 2001
From: deon <deon@dege.au>
Date: Sun, 26 May 2024 04:56:39 +0000
Subject: [PATCH] Update Installation

---
 Installation.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/Installation.md b/Installation.md
index 9cf5a60..516f12c 100644
--- a/Installation.md
+++ b/Installation.md
@@ -126,7 +126,7 @@ services:
     networks:
       default:
       public:
-        ipv6_address: [IPv6_PREFIX]:0d0c:e02::2
+        ipv6_address: [IPv6_PREFIX]:0d0c:100::2
         aliases:
           - clrghouz
     hostname: clrghouz.test.dege.au
@@ -179,7 +179,7 @@ services:
     networks:
       default:
       public:
-        ipv6_address: [IPv6_PREFIX]:0d0c:e02::3
+        ipv6_address: [IPv6_PREFIX]:0d0c:100::3
     sysctls:
     - "net.ipv6.conf.all.disable_ipv6=0"
     volumes:
@@ -271,7 +271,7 @@ services:
     networks:
       default:
       public:
-        ipv6_address: [IPv6_PREFIX]:0d0c:e02::f
+        ipv6_address: [IPv6_PREFIX]:0d0c:100::f
     ports:
     - "24553:24553"
     - "24554:24554"
@@ -292,8 +292,8 @@ networks:
     ipam:
       driver: default
       config:
-      - subnet: [IPv6_PREFIX]:0d0c:e02::/96
-        gateway: [IPv6_PREFIX]:0d0c:e02::1
+      - subnet: [IPv6_PREFIX]:0d0c:100::/96
+        gateway: [IPv6_PREFIX]:0d0c:100::1
 ```
 
 _NOTES:_
@@ -301,6 +301,7 @@ _NOTES:_
 * This docker compose file should be called `docker-compose.yml` for it to be found automatically.
 * You'll defined the `[APP_KEY]` below
 * Update the `[IPv6_PREFIX]` as appropriate for your setup. This assumes you have your IPv6 setup, and you have configured your router to route this prefix to this host running clrghouz.
+   The example I use here `[IPv6_PREFIX]:0d0c:100::/96` is because my docker hosts run many applications, and I want each application to have its own segment. So I route `[IPv6_PREFIX]:0d0c:100::/88` to the docker host, which ultimately provides me with 256 `/96` networks, with each network having more than enough addresses I can use.
 * Create a suitable `[DB_PASSWORD]` and update your docker-compose file.
 * We'll define `[MINIO_ACCESS_KEY]` and `[MINIO_SECRET_KEY]` later - and you'll update your docker-compose file with those details.
 * If you dont want to use haproxy, then you can comment/delete out this section in the docker-compose file. You'll also need to uncomment the post definitions in the _web:_ section.