bbs/clrghouz
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Update Installation

deon 2024-05-26 04:56:39 +00:00
parent 720551ede5
commit fee520c3f4
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
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.