diff --git a/README.md b/README.md index 4e518d0..540930d 100644 --- a/README.md +++ b/README.md @@ -24,9 +24,18 @@ The core of the setup is Caddy reverse proxy.
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:
+`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. diff --git a/bitwarden_rs/readme.md b/bitwarden_rs/readme.md index 4f0430a..4ae9ab8 100644 --- a/bitwarden_rs/readme.md +++ b/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
+* environment variable `WEBSOCKET_ENABLED=true` needs to be set in the `.env` file
* reverse proxy needs to route `/notifications/hub` to port 3012
* your router/firewall needs to **forward port 3012** to the docker host, same as port 80 and 443 are forwarded diff --git a/bookstack/readme.md b/bookstack/readme.md index cbee71f..b4a4d8d 100644 --- a/bookstack/readme.md +++ b/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 diff --git a/homer/readme.md b/homer/readme.md index c3130de..fed559e 100644 --- a/homer/readme.md +++ b/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 diff --git a/nextcloud/readme.md b/nextcloud/readme.md index b889b0b..458060d 100644 --- a/nextcloud/readme.md +++ b/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 diff --git a/portainer/readme.md b/portainer/readme.md index ae82458..5e241a9 100644 --- a/portainer/readme.md +++ b/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 diff --git a/prometheus_grafana/readme.md b/prometheus_grafana/readme.md index ec48a74..a42cf7a 100644 --- a/prometheus_grafana/readme.md +++ b/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 diff --git a/watchtower/readme.md b/watchtower/readme.md index cddb2e6..bb00d5a 100644 --- a/watchtower/readme.md +++ b/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.
+Scheduled to run every saturday at midnight using environment variable.
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).