Update Installation

deon 2024-05-31 00:06:47 +00:00
parent f7d54c6614
commit 07dd2b342f

@ -339,6 +339,8 @@ _NOTES:_
* Items commented out in the `.env` file are defaults, that will be used in the `docker-compose.yml` file automatically * Items commented out in the `.env` file are defaults, that will be used in the `docker-compose.yml` file automatically
* This docker compose file should be called `docker-compose.yml` for it to be found automatically. * This docker compose file should be called `docker-compose.yml` for it to be found automatically.
* Items surrounded in `[]` brackets need to be changed (including removing the `[]`)
* Values that have a space in them, need to be surrounded in `"`, eg: `MAIL_FROM_NAME="Bart Simpson"`
* You'll defined the `[APP_KEY]` below * 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. * 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:f1d0::/112` is because my docker hosts run many applications, and I want each application to have its own segment. So I route `[IPv6_PREFIX]:0d0c:0100::/88` to the docker host, which ultimately provides me with lots of `/112` networks, with each network having more than enough addresses I can use. The example I use here `[IPv6_PREFIX]:0d0c:100:f1d0::/112` is because my docker hosts run many applications, and I want each application to have its own segment. So I route `[IPv6_PREFIX]:0d0c:0100::/88` to the docker host, which ultimately provides me with lots of `/112` networks, with each network having more than enough addresses I can use.