Update Installation

deon 2024-05-28 07:58:24 +00:00
parent 5c203fbb0f
commit c7e77500b4

@ -361,3 +361,61 @@ base64:iT+8vM9p0X8oupGPKF+/ZqAxqyIQY5dWd72TaAlfcdY= <--- WHAT IS HERE IS YOUR KE
``` ```
And update the docker-compose file and replace `[APP_KEY]` with this key. And update the docker-compose file and replace `[APP_KEY]` with this key.
## Create a start/stop script (optional, but helpful)
Create a script "up" to fresh the container images (if they have been updated) and start clrghouz.
```sh
#!/bin/sh
docker compose pull
docker compose up --no-start
docker compose start
```
If you want a corresponding "down" script,
```
#!/bin/sh
docker compose down
```
Ultimately you can name these whatever you like, I name mine `up.sh` and `down.sh` respectively. (Dont forget to make them executable with `chmod +x up.sh down.sh`.
## Start clrghouz
Using your new script, you can start clrghouz (you dont need to do this as root, if your user id is a member of the `docker` group - which was an earlier step).
(Or if you didnt make a script `docker compose up` will do it.)
```sh
$ ./up.sh
[+] Pulling 7/7
✔ queue Skipped - Image is already being pulled by web
✔ schedule Skipped - Image is already being pulled by web
✔ postgres Pulled
✔ haproxy Pulled
✔ web Pulled
✔ memcached Pulled
✔ minio Pulled
[+] Creating 9/9
✔ Network clrghouz_default Created
✔ Network clrghouz_public Created
✔ Container clrghouz-haproxy-1 Created
✔ Container clrghouz-memcached-1 Created
✔ Container clrghouz-postgres-1 Created
✔ Container clrghouz-minio-1 Created
✔ Container clrghouz-schedule-1 Created
✔ Container clrghouz-web-1 Created
✔ Container clrghouz-queue-1 Created
[+] Running 7/7
✔ Container clrghouz-haproxy-1 Started
✔ Container clrghouz-memcached-1 Started
✔ Container clrghouz-postgres-1 Started
✔ Container clrghouz-minio-1 Started
✔ Container clrghouz-queue-1 Started
✔ Container clrghouz-schedule-1 Started
✔ Container clrghouz-web-1 Started
```