v1.4.2 release

This commit is contained in:
bunkerity 2022-06-27 17:32:15 +02:00
parent c0a8a356c2
commit f7290b2c79
No known key found for this signature in database
GPG Key ID: 3D80806F12602A7C
43 changed files with 100 additions and 100 deletions

View File

@ -3,7 +3,7 @@
</p>
<p align="center">
<img src="https://img.shields.io/badge/bunkerweb-1.4.1-blue" />
<img src="https://img.shields.io/badge/bunkerweb-1.4.2-blue" />
<img src="https://img.shields.io/github/last-commit/bunkerity/bunkerweb" />
<img src="https://img.shields.io/github/workflow/status/bunkerity/bunkerweb/Automatic%20test%2C%20build%2C%20push%20and%20deploy%20%28DEV%29?label=CI%2FCD%20dev" />
<img src="https://img.shields.io/github/workflow/status/bunkerity/bunkerweb/Automatic%20test%2C%20build%2C%20push%20and%20deploy%20%28PROD%29?label=CI%2FCD%20prod" />

View File

@ -1 +1 @@
1.4.1
1.4.2

View File

@ -12,7 +12,7 @@ Using BunkerWeb as a [Docker](https://www.docker.com/) container is a quick and
We provide ready to use prebuilt images for x64, x86 armv8 and armv7 architectures on [Docker Hub](https://hub.docker.com/r/bunkerity/bunkerweb) :
```shell
docker pull bunkerity/bunkerweb:1.4.1
docker pull bunkerity/bunkerweb:1.4.2
```
Alternatively, you can build the Docker images directly from the [source](https://github.com/bunkerity/bunkerweb) (and take a coffee ☕ because it may be long depending on your hardware) :
@ -39,7 +39,7 @@ docker run \
-e MY_SETTING=value \
-e "MY_OTHER_SETTING=value with spaces" \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
@ -48,7 +48,7 @@ Here is the docker-compose equivalent :
...
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
environment:
- MY_SETTING=value
```
@ -73,7 +73,7 @@ docker run \
...
-v "${PWD}/bw-data:/data" \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
@ -82,7 +82,7 @@ Here is the docker-compose equivalent :
...
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
volumes:
- bw-data:/data
...
@ -109,7 +109,7 @@ docker run \
...
-v ./bw-data:/data \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
@ -119,7 +119,7 @@ Here is the docker-compose equivalent :
...
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
volumes:
- ./bw-data:/data
```
@ -141,7 +141,7 @@ docker run \
...
--network mynetwork \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
You will also need to do the same with your web application(s). Please note that the other containers are accessible using their name as the hostname.
@ -152,7 +152,7 @@ Here is the docker-compose equivalent :
...
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
networks:
- bw-net
...
@ -207,7 +207,7 @@ docker run \
-e SERVER_NAME= \
-e "API_WHITELIST_IP=127.0.0.0/8 10.20.30.0/24" \
-l bunkerweb.AUTOCONF \
bunkerity/bunkerweb:1.4.1 && \
bunkerity/bunkerweb:1.4.2 && \
docker network connect bw-services mybunker
```
@ -221,7 +221,7 @@ docker run \
--network bw-autoconf \
-v bw-data:/data \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
bunkerity/bunkerweb-autoconf:1.4.1
bunkerity/bunkerweb-autoconf:1.4.2
```
Here is the docker-compose equivalent for the BunkerWeb autoconf stack :
@ -232,7 +232,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443
@ -248,7 +248,7 @@ services:
- bw-services
myautoconf:
image: bunkerity/bunkerweb-autoconf:1.4.1
image: bunkerity/bunkerweb-autoconf:1.4.2
volumes:
- bw-data:/data
- /var/run/docker.sock:/var/run/docker.sock:ro
@ -350,7 +350,7 @@ docker service create \
-e MULTISITE=yes \
-e "API_WHITELIST_IP=127.0.0.0/8 10.20.30.0/24" \
-l bunkerweb.AUTOCONF \
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
And the autoconf one :
@ -364,7 +364,7 @@ docker service \
--mount type=bind,source=/var/run/docker.sock,destination=/var/run/docker.sock,ro \
--mount type=volume,source=bw-data,destination=/data \
-e SWARM_MODE=yes \
bunkerity/bunkerweb-autoconf:1.4.1
bunkerity/bunkerweb-autoconf:1.4.2
```
Here is the docker-compose equivalent (using `docker stack deploy`) :
@ -375,7 +375,7 @@ version: '3.5'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- published: 80
target: 8080
@ -402,7 +402,7 @@ services:
- "bunkerweb.AUTOCONF"
myautoconf:
image: bunkerity/bunkerweb-autoconf:1.4.1
image: bunkerity/bunkerweb-autoconf:1.4.2
environment:
- SWARM_MODE=yes
volumes:
@ -692,11 +692,11 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt
sudo apt install -y nginx=1.20.2-1~bullseye
```
And finally install BunkerWeb 1.4.1 :
And finally install BunkerWeb 1.4.2 :
```shell
curl -s https://packagecloud.io/install/repositories/bunkerity/bunkerweb/script.deb.sh | sudo bash && \
sudo apt update && \
sudo apt install -y bunkerweb=1.4.1
sudo apt install -y bunkerweb=1.4.2
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command :
@ -722,11 +722,11 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt
sudo apt install -y nginx=1.20.2-1~jammy
```
And finally install BunkerWeb 1.4.1 :
And finally install BunkerWeb 1.4.2 :
```shell
curl -s https://packagecloud.io/install/repositories/bunkerity/bunkerweb/script.deb.sh | sudo bash && \
sudo apt update && \
sudo apt install -y bunkerweb=1.4.1
sudo apt install -y bunkerweb=1.4.2
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command :
@ -744,7 +744,7 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt
```shell
curl -s https://packagecloud.io/install/repositories/bunkerity/bunkerweb/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo dnf install -y bunkerweb-1.4.1
sudo dnf install -y bunkerweb-1.4.2
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command :
@ -771,12 +771,12 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt
sudo dnf install nginx-1.20.2
```
And finally install BunkerWeb 1.4.1 :
And finally install BunkerWeb 1.4.2 :
```shell
dnf install -y epel-release && \
curl -s https://packagecloud.io/install/repositories/bunkerity/bunkerweb/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo dnf install -y bunkerweb-1.4.1
sudo dnf install -y bunkerweb-1.4.2
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command :

View File

@ -53,13 +53,13 @@ The first step is to install the plugin by putting the plugin files inside the c
...
-v "${PWD}/bw-data:/data" \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
volumes:
- ./bw-data:/data
...

View File

@ -54,7 +54,7 @@ You will find more settings about reverse proxy in the [settings section](/1.4/s
-e USE_REVERSE_PROXY=yes \
-e REVERSE_PROXY_URL=/ \
-e REVERSE_PROXY_HOST=http://myapp \
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
@ -64,7 +64,7 @@ You will find more settings about reverse proxy in the [settings section](/1.4/s
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443
@ -331,7 +331,7 @@ You will find more settings about reverse proxy in the [settings section](/1.4/s
-e app1.example.com_REVERSE_PROXY_HOST=http://myapp1 \
-e app2.example.com_REVERSE_PROXY_HOST=http://myapp2 \
-e app3.example.com_REVERSE_PROXY_HOST=http://myapp3 \
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
@ -341,7 +341,7 @@ You will find more settings about reverse proxy in the [settings section](/1.4/s
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443
@ -875,13 +875,13 @@ REAL_IP_HEADER=X-Forwarded-For
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=X-Forwarded-For \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -900,13 +900,13 @@ REAL_IP_HEADER=X-Forwarded-For
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=X-Forwarded-For \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -925,13 +925,13 @@ REAL_IP_HEADER=X-Forwarded-For
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=X-Forwarded-For \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent (using `docker stack deploy`) :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -956,7 +956,7 @@ REAL_IP_HEADER=X-Forwarded-For
spec:
containers:
- name: bunkerweb
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
env:
- name: USE_REAL_IP
@ -1008,13 +1008,13 @@ REAL_IP_HEADER=proxy_protocol
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=proxy_protocol \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -1035,13 +1035,13 @@ REAL_IP_HEADER=proxy_protocol
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=proxy_protocol \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -1062,13 +1062,13 @@ REAL_IP_HEADER=proxy_protocol
-e "REAL_IP_FROM=1.2.3.0/24 100.64.0.0/16" \
-e REAL_IP_HEADER=proxy_protocol \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent (using `docker stack deploy`) :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
environment:
- USE_REAL_IP=yes
@ -1094,7 +1094,7 @@ REAL_IP_HEADER=proxy_protocol
spec:
containers:
- name: bunkerweb
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
...
env:
- name: USE_REAL_IP
@ -1169,13 +1169,13 @@ Some integrations offer a more convenient way of applying configurations for exa
...
-v "${PWD}/bw-data:/data" \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
volumes:
- ./bw-data:/data
...
@ -1212,13 +1212,13 @@ Some integrations offer a more convenient way of applying configurations for exa
...
-v "${PWD}/bw-data:/data" \
...
bunkerity/bunkerweb:1.4.1
bunkerity/bunkerweb:1.4.2
```
Here is the docker-compose equivalent :
```yaml
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
volumes:
- ./bw-data:/data
...

View File

@ -203,14 +203,14 @@ You can manually unban an IP which can be useful when doing some tests but it ne
=== "Docker autoconf"
You can use the `docker exec` command (replace `mya` with the name of your container) :
You can use the `docker exec` command (replace `myautoconf` with the name of your container) :
```shell
docker exec mybunker bwcli unban 1.2.3.4
docker exec myautoconf bwcli unban 1.2.3.4
```
Here is the docker-compose equivalent (replace `mybunker` with the name of the services declared in the docker-compose.yml file) :
Here is the docker-compose equivalent (replace `myautoconf` with the name of the services declared in the docker-compose.yml file) :
```shell
docker-compose exec mybunker bwcli unban 1.2.3.4
docker-compose exec myautoconf bwcli unban 1.2.3.4
```
=== "Swarm"
@ -229,9 +229,9 @@ You can manually unban an IP which can be useful when doing some tests but it ne
=== "Linux"
You can use the `bwcli` command :
You can use the `bwcli` command (as root) :
```shell
bwcli unban 1.2.3.4
sudo bwcli unban 1.2.3.4
```
## Whitelisting

View File

@ -78,7 +78,7 @@ Because the web UI is a web application, the recommended installation procedure
-e "bwadm.example.com_REVERSE_PROXY_HEADER=X-Script-Name /changeme" \
-e bwadm.example.com_REVERSE_PROXY_INTERCEPT_ERRORS=no \
-l bunkerweb.UI \
bunkerity/bunkerweb:1.4.1 && \
bunkerity/bunkerweb:1.4.2 && \
docker network connect bw-ui mybunker
```
@ -117,7 +117,7 @@ Because the web UI is a web application, the recommended installation procedure
-e ADMIN_USERNAME=admin \
-e ADMIN_PASSWORD=changeme \
-e ABSOLUTE_URI=http(s)://bwadm.example.com/changeme/
bunkerity/bunkerweb-ui:1.4.1 && \
bunkerity/bunkerweb-ui:1.4.2 && \
docker network connect bw-docker myui
```
@ -133,7 +133,7 @@ Because the web UI is a web application, the recommended installation procedure
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
networks:
- bw-services
- bw-ui
@ -156,7 +156,7 @@ Because the web UI is a web application, the recommended installation procedure
- "bunkerweb.UI"
myui:
image: bunkerity/bunkerweb-ui:1.4.1
image: bunkerity/bunkerweb-ui:1.4.2
depends_on:
- mydocker
networks:

View File

@ -3,7 +3,7 @@ version: '3.4'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3.4'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
# ⚠️ read this if you use local folders for volumes ⚠️
# bunkerweb runs as an unprivileged user with UID/GID 101
# don't forget to edit the permissions of the files and folders accordingly

View File

@ -27,7 +27,7 @@ services:
...
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
# dropping all capabilities
cap_drop:
- ALL

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -24,7 +24,7 @@ services:
- mongo
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
# ⚠️ read this if you use local folders for volumes ⚠️
# bunkerweb runs as an unprivileged user with UID/GID 101
# don't forget to edit the permissions of the files and folders accordingly

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
logging:
driver: syslog
options:

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -11,7 +11,7 @@ services:
- SERVICE1_TOR_SERVICE_VERSION=3
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
# ⚠️ read this if you use local folders for volumes ⚠️
# bunkerweb runs as an unprivileged user with UID/GID 101
# don't forget to edit the permissions of the files and folders accordingly

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443
@ -42,7 +42,7 @@ services:
- net_svc
myui:
image: bunkerity/bunkerweb-ui:1.4.1
image: bunkerity/bunkerweb-ui:1.4.2
depends_on:
- myuiproxy
volumes:

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443

View File

@ -3,7 +3,7 @@ version: '3'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- 80:8080
- 443:8443
@ -20,7 +20,7 @@ services:
- bw-services
myautoconf:
image: bunkerity/bunkerweb-autoconf:1.4.1
image: bunkerity/bunkerweb-autoconf:1.4.2
volumes:
- ./bw-data:/data
- /var/run/docker.sock:/var/run/docker.sock:ro

View File

@ -16,7 +16,7 @@ spec:
spec:
containers:
- name: bunkerweb
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
imagePullPolicy: Always
securityContext:
runAsUser: 101
@ -106,7 +106,7 @@ spec:
claimName: pvc-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.4.1
image: bunkerity/bunkerweb-autoconf:1.4.2
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE

View File

@ -3,7 +3,7 @@ version: '3.5'
services:
mybunker:
image: bunkerity/bunkerweb:1.4.1
image: bunkerity/bunkerweb:1.4.2
ports:
- published: 80
target: 8080
@ -31,7 +31,7 @@ services:
- "bunkerweb.AUTOCONF"
myautoconf:
image: bunkerity/bunkerweb-autoconf:1.4.1
image: bunkerity/bunkerweb-autoconf:1.4.2
environment:
- SWARM_MODE=yes
volumes: