update

README.md

@@ -24,9 +24,18 @@
 The core of the setup is Caddy reverse proxy.</br>
 It's described in most details.
 
-# Some docker basics and some info
+# Some extra info
 
-### Compose and environment variables
+### Caddy 
+
+When making changes to Caddyfile, the config needs to be reloaded afterwards.
+
+On the docker host:<br>
+`docker exec -w /etc/caddy caddy caddy reload`
+
+Assuming container name is kept as `caddy`.
+
+### Compose
 
 When making changes use `docker-compose down` and `docker-compose up -d`,
 not just restart or stop/start.

bitwarden_rs/readme.md

@@ -43,7 +43,7 @@ only the server is a different implementation.
 ```
 
 * `bitwarden-data/` - a directory where bitwarden will store its database and other data
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the container
 * `bitwarden-backup-script.sh` - a backup script if you want it
 
@@ -139,7 +139,7 @@ bitwarden.{$MY_DOMAIN} {
 so that all web based clients, including desktop app,
 can immediately sync when a change happens on the server.
 
-* environmental variable `WEBSOCKET_ENABLED=true` needs to be set in the `.env` file</br>
+* environment variable `WEBSOCKET_ENABLED=true` needs to be set in the `.env` file</br>
 * reverse proxy needs to route `/notifications/hub` to port 3012</br>
 * your router/firewall needs to **forward port 3012** to the docker host,
 same as port 80 and 443 are forwarded

bookstack/readme.md

@@ -36,7 +36,7 @@ which uses nginx as a web server.
 
 * `bookstack-data/` - a directory where bookstack will store its web app data
 * `bookstack-db-data/` - a directory where bookstack will store its MySQL database data
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the containers
 * `bookstack-backup-script.sh` - a backup script if you want it
 

homer/readme.md

@@ -29,7 +29,7 @@ The docker image uses darkhttpd simple web server on alpine linux.
 ```
 
 * `assets/` - a directory containing icons and other directories with icons
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the container
 * `config.yml` - homer's configuration file bind mounted in to the container
 

nextcloud/readme.md

@@ -44,7 +44,7 @@ and for [memory file caching](https://docs.nextcloud.com/server/latest/admin_man
 
 * `nextcloud-data/` - a directory where nextcloud will store users data and web app data
 * `nextcloud-db-data/` - a directory where nextcloud will store its database data
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the containers
 * `nginx.conf` - nginx web server configuration file
 * `nextcloud-backup-script.sh` - a backup script if you want it

portainer/readme.md

@@ -30,7 +30,7 @@ In my use it is mostly information tool, rather than a management tool.
 ```
 
 * `portainer-data/` - a directory where portainer stores its peristent data
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker
   how to build the containers
 

prometheus_grafana/readme.md

@@ -78,7 +78,7 @@ and consists of several components.
 * `grafana/` - a directory containing grafanas configs and dashboards
 * `grafana-data/` - a directory where grafana stores its data
 * `prometheus-data/` - a directory where prometheus stores its database and data
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the containers
 * `prometheus.yml` - a configuration file for prometheus
 

watchtower/readme.md

@@ -30,14 +30,14 @@ This can be bandwidth intensive, so its scheduled checks should account for this
             └── docker-compose.yml
 ```
 
-* `.env` - a file containing environmental variables for docker compose
+* `.env` - a file containing environment variables for docker compose
 * `docker-compose.yml` - a docker compose file, telling docker how to build the container
 
 Only these two files must be provided.
 
 # docker-compose
 
-Scheduled to run every saturday at midnight using environmental variable.</br>
+Scheduled to run every saturday at midnight using environment variable.</br>
 Heads up that not a typical cron format is used,
 [seconds are the first digit](https://pkg.go.dev/github.com/robfig/cron@v1.2.0?tab=doc#hdr-CRON_Expression_Format).