diff --git a/docs/backup-new-integrations.md b/docs/backup-new-integrations.md index fbb0b039f..ee85caa82 100644 --- a/docs/backup-new-integrations.md +++ b/docs/backup-new-integrations.md @@ -96,7 +96,7 @@ vagrant ssh python3 -m http.server -b 127.0.0.1 ``` - Configuration of BunkerWeb is done by editing the `/opt/bunkerweb/variables.env` file. + Configuration of BunkerWeb is done by editing the `/etc/bunkerweb/variables.env` file. Connect to your vagrant machine : ```shell @@ -159,7 +159,7 @@ vagrant ssh vagrant ssh ``` - Configuration of BunkerWeb is done by editing the /opt/bunkerweb/variables.env file : + Configuration of BunkerWeb is done by editing the /etc/bunkerweb/variables.env file : ```conf SERVER_NAME=app1.example.com app2.example.com app3.example.com HTTP_PORT=80 @@ -190,7 +190,7 @@ vagrant ssh === "Vagrant" - You will need to add the settings to the `/opt/bunkerweb/variables.env` file : + You will need to add the settings to the `/etc/bunkerweb/variables.env` file : ```conf ... @@ -204,7 +204,7 @@ vagrant ssh === "Vagrant" - You will need to add the settings to the `/opt/bunkerweb/variables.env` file : + You will need to add the settings to the `/etc/bunkerweb/variables.env` file : ```conf ... @@ -219,7 +219,7 @@ vagrant ssh === "Vagrant" - When using the [Vagrant integration](/1.4/integrations/#vagrant), custom configurations must be written to the `/opt/bunkerweb/configs` folder. + When using the [Vagrant integration](/1.4/integrations/#vagrant), custom configurations must be written to the `/etc/bunkerweb/configs` folder. Here is an example for server-http/hello-world.conf : ```conf @@ -233,8 +233,8 @@ vagrant ssh Because BunkerWeb runs as an unprivileged user (nginx:nginx), you will need to edit the permissions : ```shell - chown -R root:nginx /opt/bunkerweb/configs && \ - chmod -R 770 /opt/bunkerweb/configs + chown -R root:nginx /etc/bunkerweb/configs && \ + chmod -R 770 /etc/bunkerweb/configs ``` Don't forget to restart the BunkerWeb service once it's done. @@ -243,9 +243,9 @@ vagrant ssh We will assume that you already have the [Vagrant integration](/1.4/integrations/#vagrant) stack running on your machine. - By default, BunkerWeb will search for web files inside the `/opt/bunkerweb/www` folder. You can use it to store your PHP application. Please note that you will need to configure your PHP-FPM service to get or set the user/group of the running processes and the UNIX socket file used to communicate with BunkerWeb. + By default, BunkerWeb will search for web files inside the `/var/www/html` folder. You can use it to store your PHP application. Please note that you will need to configure your PHP-FPM service to get or set the user/group of the running processes and the UNIX socket file used to communicate with BunkerWeb. - First of all, you will need to make sure that your PHP-FPM instance can access the files inside the `/opt/bunkerweb/www` folder and also that BunkerWeb can access the UNIX socket file in order to communicate with PHP-FPM. We recommend to set a different user like `www-data` for the PHP-FPM service and to give the nginx group access to the UNIX socket file. Here is corresponding PHP-FPM configuration : + First of all, you will need to make sure that your PHP-FPM instance can access the files inside the `/var/www/html` folder and also that BunkerWeb can access the UNIX socket file in order to communicate with PHP-FPM. We recommend to set a different user like `www-data` for the PHP-FPM service and to give the nginx group access to the UNIX socket file. Here is corresponding PHP-FPM configuration : ```ini ... [www] @@ -263,14 +263,14 @@ vagrant ssh systemctl restart php8.1-fpm ``` - Once your application is copied to the `/opt/bunkerweb/www` folder, you will need to fix the permissions so BunkerWeb (user/group nginx) can at least read files and list folders and PHP-FPM (user/group www-data) is the owner of the files and folders : + Once your application is copied to the `/var/www/html` folder, you will need to fix the permissions so BunkerWeb (user/group nginx) can at least read files and list folders and PHP-FPM (user/group www-data) is the owner of the files and folders : ```shell - chown -R www-data:nginx /opt/bunkerweb/www && \ - find /opt/bunkerweb/www -type f -exec chmod 0640 {} \; && \ - find /opt/bunkerweb/www -type d -exec chmod 0750 {} \; + chown -R www-data:nginx /var/www/html && \ + find /var/www/html -type f -exec chmod 0640 {} \; && \ + find /var/www/html -type d -exec chmod 0750 {} \; ``` - You can now edit the `/opt/bunkerweb/variable.env` file : + You can now edit the `/etc/bunkerweb/variable.env` file : ```env HTTP_PORT=80 HTTPS_PORT=443 @@ -278,7 +278,7 @@ vagrant ssh SERVER_NAME=www.example.com AUTO_LETS_ENCRYPT=yes LOCAL_PHP=/run/php/php-fpm.sock - LOCAL_PHP_PATH=/opt/bunkerweb/www/ + LOCAL_PHP_PATH=/var/www/html/ ``` Let's check the status of BunkerWeb : @@ -299,9 +299,9 @@ vagrant ssh We will assume that you already have the [Vagrant integration](/1.4/integrations/#vagrant) stack running on your machine. - By default, BunkerWeb will search for web files inside the `/opt/bunkerweb/www` folder. You can use it to store your PHP applications : each application will be in its own subfolder named the same as the primary server name. Please note that you will need to configure your PHP-FPM service to get or set the user/group of the running processes and the UNIX socket file used to communicate with BunkerWeb. + By default, BunkerWeb will search for web files inside the `/var/www/html` folder. You can use it to store your PHP applications : each application will be in its own subfolder named the same as the primary server name. Please note that you will need to configure your PHP-FPM service to get or set the user/group of the running processes and the UNIX socket file used to communicate with BunkerWeb. - First of all, you will need to make sure that your PHP-FPM instance can access the files inside the `/opt/bunkerweb/www` folder and also that BunkerWeb can access the UNIX socket file in order to communicate with PHP-FPM. We recommend to set a different user like `www-data` for the PHP-FPM service and to give the nginx group access to the UNIX socket file. Here is corresponding PHP-FPM configuration : + First of all, you will need to make sure that your PHP-FPM instance can access the files inside the `/var/www/html` folder and also that BunkerWeb can access the UNIX socket file in order to communicate with PHP-FPM. We recommend to set a different user like `www-data` for the PHP-FPM service and to give the nginx group access to the UNIX socket file. Here is corresponding PHP-FPM configuration : ```ini ... [www] @@ -319,14 +319,14 @@ vagrant ssh systemctl restart php8.1-fpm ``` - Once your application is copied to the `/opt/bunkerweb/www` folder, you will need to fix the permissions so BunkerWeb (user/group nginx) can at least read files and list folders and PHP-FPM (user/group www-data) is the owner of the files and folders : + Once your application is copied to the `/var/www/html` folder, you will need to fix the permissions so BunkerWeb (user/group nginx) can at least read files and list folders and PHP-FPM (user/group www-data) is the owner of the files and folders : ```shell - chown -R www-data:nginx /opt/bunkerweb/www && \ - find /opt/bunkerweb/www -type f -exec chmod 0640 {} \; && \ - find /opt/bunkerweb/www -type d -exec chmod 0750 {} \; + chown -R www-data:nginx /var/www/html && \ + find /var/www/html -type f -exec chmod 0640 {} \; && \ + find /var/www/html -type d -exec chmod 0750 {} \; ``` - You can now edit the `/opt/bunkerweb/variable.env` file : + You can now edit the `/etc/bunkerweb/variable.env` file : ```env HTTP_PORT=80 HTTPS_PORT=443 @@ -335,11 +335,11 @@ vagrant ssh MULTISITE=yes AUTO_LETS_ENCRYPT=yes app1.example.com_LOCAL_PHP=/run/php/php-fpm.sock - app1.example.com_LOCAL_PHP_PATH=/opt/bunkerweb/www/app1.example.com + app1.example.com_LOCAL_PHP_PATH=/var/www/html/app1.example.com app2.example.com_LOCAL_PHP=/run/php/php-fpm.sock - app2.example.com_LOCAL_PHP_PATH=/opt/bunkerweb/www/app2.example.com + app2.example.com_LOCAL_PHP_PATH=/var/www/html/app2.example.com app3.example.com_LOCAL_PHP=/run/php/php-fpm.sock - app3.example.com_LOCAL_PHP_PATH=/opt/bunkerweb/www/app3.example.com + app3.example.com_LOCAL_PHP_PATH=/var/www/html/app3.example.com ``` Let's check the status of BunkerWeb : @@ -360,7 +360,7 @@ vagrant ssh === "Vagrant" - When using the [Linux integration](/1.4/integrations/#linux), plugins must be written to the `/opt/bunkerweb/plugins` folder : + When using the [Linux integration](/1.4/integrations/#linux), plugins must be written to the `/etc/bunkerweb/plugins` folder : ```shell git clone https://github.com/bunkerity/bunkerweb-plugins && \ cp -rp ./bunkerweb-plugins/* /data/plugins @@ -372,7 +372,7 @@ vagrant ssh The installation of the web UI using the [Vagrant integration](/1.4/integrations/#vagrant) is pretty straightforward because it is installed with BunkerWeb. - The first thing to do is to edit the BunkerWeb configuration located at **/opt/bunkerweb/variables.env** to add settings related to the web UI : + The first thing to do is to edit the BunkerWeb configuration located at **/etc/bunkerweb/variables.env** to add settings related to the web UI : ```conf HTTP_PORT=80 HTTPS_PORT=443 @@ -401,7 +401,7 @@ vagrant ssh systemctl restart bunkerweb ``` - You can edit the **/opt/bunkerweb/ui.env** file containing the settings of the web UI : + You can edit the **/etc/bunkerweb/ui.env** file containing the settings of the web UI : ```conf ADMIN_USERNAME=admin ADMIN_PASSWORD=changeme @@ -410,7 +410,7 @@ vagrant ssh Important things to note : - * `http(s)://bwadmin.example.com/changeme/` is the full base URL of the web UI (must match the sub(domain) and /changeme URL used in **/opt/bunkerweb/variables.env**) + * `http(s)://bwadmin.example.com/changeme/` is the full base URL of the web UI (must match the sub(domain) and /changeme URL used in **/etc/bunkerweb/variables.env**) * replace the username `admin` and password `changeme` with strong ones Restart the BunkerWeb UI service and you are now ready to access it : diff --git a/docs/integrations.md b/docs/integrations.md index a2eeb5720..f50051ccb 100644 --- a/docs/integrations.md +++ b/docs/integrations.md @@ -3,7 +3,7 @@ ## Docker
- ![Overwiew](assets/img/integration-docker.svg){ align=center } + ![Overview](assets/img/integration-docker.svg){ align=center }
Docker integration
@@ -174,7 +174,7 @@ networks: ## Docker autoconf
- ![Overwiew](assets/img/integration-autoconf.svg){ align=center } + ![Overview](assets/img/integration-autoconf.svg){ align=center }
Docker autoconf integration
@@ -325,7 +325,7 @@ networks: ## Swarm
- ![Overwiew](assets/img/integration-swarm.svg){ align=center } + ![Overview](assets/img/integration-swarm.svg){ align=center }
Docker Swarm integration
@@ -486,7 +486,7 @@ networks: ## Kubernetes
- ![Overwiew](assets/img/integration-kubernetes.svg){ align=center } + ![Overview](assets/img/integration-kubernetes.svg){ align=center }
Kubernetes integration
@@ -580,7 +580,7 @@ spec: livenessProbe: exec: command: - - /opt/bunkerweb/helpers/healthcheck.sh + - /usr/share/bunkerweb/helpers/healthcheck.sh initialDelaySeconds: 30 periodSeconds: 5 timeoutSeconds: 1 @@ -588,7 +588,7 @@ spec: readinessProbe: exec: command: - - /opt/bunkerweb/helpers/healthcheck.sh + - /usr/share/bunkerweb/helpers/healthcheck.sh initialDelaySeconds: 30 periodSeconds: 1 timeoutSeconds: 1 @@ -673,7 +673,7 @@ spec: ## Linux
- ![Overwiew](assets/img/integration-linux.svg){ align=center } + ![Overview](assets/img/integration-linux.svg){ align=center }
Linux integration
@@ -806,9 +806,9 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt The first step is to install NGINX 1.20.2 using the repository of your choice or by [compiling it from source](https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/#compiling-and-installing-from-source). - The target installation folder of BunkerWeb is located at `/opt/bunkerweb`, let's create it : + The target installation folder of BunkerWeb is located at `/usr/share/bunkerweb`, let's create it : ```shell - mkdir /opt/bunkerweb + mkdir /usr/share/bunkerweb ``` You can now clone the BunkerWeb project to the `/tmp` folder : @@ -816,40 +816,42 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt https://github.com/bunkerity/bunkerweb.git /tmp/bunkerweb ``` - BunkerWeb needs some dependencies to be compiled and installed to `/opt/bunkerweb/deps`, the easiest way to do it is by executing the [install.sh helper script](https://github.com/bunkerity/bunkerweb/blob/master/deps/install.sh) (please note that you will need to install additional packages which is not covered in this procedure and depends on your own system) : + BunkerWeb needs some dependencies to be compiled and installed to `/usr/share/bunkerweb/deps`, the easiest way to do it is by executing the [install.sh helper script](https://github.com/bunkerity/bunkerweb/blob/master/deps/install.sh) (please note that you will need to install additional packages which is not covered in this procedure and depends on your own system) : ``` - mkdir /opt/bunkerweb/deps && \ + mkdir /usr/share/bunkerweb/deps && \ /tmp/bunkerweb/deps/install.sh ``` - Additional Python dependencies needs to be installed into the `/opt/bunkerweb/deps/python` folder : + Additional Python dependencies needs to be installed into the `/usr/share/bunkerweb/deps/python` folder : ```shell - mkdir /opt/bunkerweb/deps/python && \ - pip install --no-cache-dir --require-hashes --target /opt/bunkerweb/deps/python -r /tmp/bunkerweb/deps/requirements.txt && \ - pip install --no-cache-dir --target /opt/bunkerweb/deps/python -r /tmp/bunkerweb/ui/requirements.txt + mkdir /usr/share/bunkerweb/deps/python && \ + pip install --no-cache-dir --require-hashes --target /usr/share/bunkerweb/deps/python -r /tmp/bunkerweb/deps/requirements.txt && \ + pip install --no-cache-dir --target /usr/share/bunkerweb/deps/python -r /tmp/bunkerweb/ui/requirements.txt ``` - Once dependencies are installed, you will be able to copy the BunkerWeb sources to the target `/opt/bunkerweb` folder : + Once dependencies are installed, you will be able to copy the BunkerWeb sources to the target `/usr/share/bunkerweb` folder : ```shell for src in api cli confs core gen helpers job lua misc utils ui settings.json VERSION linux/variables.env linux/ui.env linux/scripts ; do - cp -r /tmp/bunkerweb/${src} /opt/bunkerweb + cp -r /tmp/bunkerweb/${src} /usr/share/bunkerweb done - cp /opt/bunkerweb/helpers/bwcli /usr/local/bin + cp /usr/share/bunkerweb/helpers/bwcli /usr/local/bin ``` Additional folders also need to be created : ```shell - mkdir /opt/bunkerweb/{configs,cache,plugins,tmp} + mkdir -p /etc/bunkerweb/{configs,plugins} && \ + mkdir -p /var/cache/bunkerweb && \ + mkdir -p /var/tmp/bunkerweb ``` Permissions needs to be fixed : ```shell - find /opt/bunkerweb -path /opt/bunkerweb/deps -prune -o -type f -exec chmod 0740 {} \; && \ - find /opt/bunkerweb -path /opt/bunkerweb/deps -prune -o -type d -exec chmod 0750 {} \; && \ - find /opt/bunkerweb/core/*/jobs/* -type f -exec chmod 750 {} \; && \ - chmod 770 /opt/bunkerweb/cache /opt/bunkerweb/tmp && \ - chmod 750 /opt/bunkerweb/gen/main.py /opt/bunkerweb/job/main.py /opt/bunkerweb/cli/main.py /opt/bunkerweb/helpers/*.sh /opt/bunkerweb/scripts/*.sh /usr/local/bin/bwcli /opt/bunkerweb/ui/main.py && \ - chown -R root:nginx /opt/bunkerweb + find /usr/share/bunkerweb -path /usr/share/bunkerweb/deps -prune -o -type f -exec chmod 0740 {} \; && \ + find /usr/share/bunkerweb -path /usr/share/bunkerweb/deps -prune -o -type d -exec chmod 0750 {} \; && \ + find /usr/share/bunkerweb/core/*/jobs/* -type f -exec chmod 750 {} \; && \ + chmod 770 /var/cache/bunkerweb /var/tmp/bunkerweb && \ + chmod 750 /usr/share/bunkerweb/gen/main.py /usr/share/bunkerweb/scheduler/main.py /usr/share/bunkerweb/cli/main.py /usr/share/bunkerweb/helpers/*.sh /usr/share/bunkerweb/scripts/*.sh /usr/bin/bwcli /usr/share/bunkerweb/ui/main.py && \ + chown -R root:nginx /usr/share/bunkerweb ``` Last but not least, you will need to set up systemd unit files : @@ -862,7 +864,7 @@ Repositories of Linux packages for BunkerWeb are available on [PackageCloud](htt systemctl enable bunkerweb-ui ``` -The configuration of BunkerWeb is done by editing the `/opt/bunkerweb/variables.env` file : +The configuration of BunkerWeb is done by editing the `/etc/bunkerweb/variables.env` file : ```conf MY_SETTING_1=value1 @@ -880,7 +882,7 @@ BunkerWeb is managed using systemctl : ## Ansible
- ![Overwiew](assets/img/integration-ansible.svg){ align=center } + ![Overview](assets/img/integration-ansible.svg){ align=center }
Ansible integration
@@ -938,4 +940,88 @@ Configuration of BunkerWeb is done by using specific role variables : | `custom_www` | string | Path of the www directory to upload. | empty value | | `custom_plugins` | string | Path of the plugins directory to upload. | empty value | | `custom_www_owner` | string | Default owner for www files and folders. | `nginx` | -| `custom_www_group` | string | Default group for www files and folders. | `nginx` | \ No newline at end of file +| `custom_www_group` | string | Default group for www files and folders. | `nginx` | + +## Vagrant + +
+ ![Overview](assets/img/integration-vagrant.svg){ align=center } +
BunkerWeb integration with Vagrant
+
+ +List of supported providers : + +- vmware_desktop +- virtualbox +- libvirt + +**_Note on Supported Base Images_** + +Please be aware that the provided Vagrant boxes are based **exclusively on Ubuntu 22.04 "Jammy"**. While BunkerWeb supports other Linux distributions, the Vagrant setup currently only supports Ubuntu 22.04 as the base operating system. This ensures a consistent and reliable environment for users who want to deploy BunkerWeb using Vagrant. + +Similar to other BunkerWeb integrations, the Vagrant setup uses **NGINX version 1.20.2**. This specific version is required to ensure compatibility and smooth functioning with BunkerWeb. Additionally, the Vagrant box includes **PHP** pre-installed, providing a ready-to-use environment for hosting PHP-based applications alongside BunkerWeb. + +By using the provided Vagrant box based on Ubuntu 22.04 "Jammy", you benefit from a well-configured and integrated setup, allowing you to focus on developing and securing your applications with BunkerWeb without worrying about the underlying infrastructure. + +Here are the steps to install BunkerWeb using Vagrant on Ubuntu with the supported virtualization providers (VirtualBox, VMware, and libvirt): + + +1. Make sure you have Vagrant and one of the supported virtualization providers (VirtualBox, VMware, or libvirt) installed on your system. +2. There are two ways to install the Vagrant box with BunkerWeb: either by using a provided Vagrantfile to configure your virtual machine or by creating a new box based on the existing BunkerWeb Vagrant box, offering you flexibility in how you set up your development environment. + +=== "Vagrantfile" + + ```shell + Vagrant.configure("2") do |config| + config.vm.box = "bunkerity/bunkerity" + end + ``` + + Depending on the virtualization provider you choose, you may need to install additional plugins: + + * For **VMware**, install the `vagrant-vmware-desktop` plugin. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + * For **libvirt**, install the `vagrant-libvirt plugin`. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + * For **VirtualBox**, install the `vagrant-vbguest` plugin. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + +=== "New Vagrant Box" + + ```shell + vagrant init bunkerity/bunkerity + ``` + + Depending on the virtualization provider you choose, you may need to install additional plugins: + + * For **VMware**, install the `vagrant-vmware-desktop` plugin. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + * For **libvirt**, install the `vagrant-libvirt plugin`. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + * For **VirtualBox**, install the `vagrant-vbguest` plugin. For more information, see the [Vagrant documentation](https://www.vagrantup.com/docs/providers). + +After installing the necessary plugins for your chosen virtualization provider, run the following command to start the virtual machine and install BunkerWeb: + +```shell +vagrant up --provider=virtualbox # or --provider=vmware_desktop or --provider=libvirt +``` + +Finally, to access the virtual machine using SSH, execute the following command: + +```shell +vagrant ssh +``` + +**Example Vagrantfile** + + Here is an example `Vagrantfile` for installing BunkerWeb on Ubuntu 22.04 "Jammy" using the different supported virtualization providers: + +```shell +Vagrant.configure("2") do |config| + # Ubuntu 22.04 "Jammy" + config.vm.box = "bunkerity/bunkerity" + # Uncomment the desired virtualization provider + # For VirtualBox (default) + config.vm.provider "virtualbox" + # For VMware + # config.vm.provider "vmware_desktop" # Windows + # config.vm.provider "vmware_workstation" # Linux + # For libvirt + # config.vm.provider "libvirt" +end +``` \ No newline at end of file diff --git a/docs/web-ui.md b/docs/web-ui.md index 9abf07d49..98e145d68 100644 --- a/docs/web-ui.md +++ b/docs/web-ui.md @@ -69,7 +69,7 @@ Because the web UI is a web application, the recommended installation procedure -e bwadm.example.com_REVERSE_PROXY_URL=/changeme/ \ -e bwadm.example.com_REVERSE_PROXY_HOST=http://bw-ui:7000 \ -e "bwadm.example.com_REVERSE_PROXY_HEADERS=X-Script-Name /changeme" \ - -e bwadm.example.com_INTERCEPTED_ERROR_CODES="400 401.5.0-beta 413 429 500 501 502 503 504" \ + -e bwadm.example.com_INTERCEPTED_ERROR_CODES="400 401 405 413 429 500 501 502 503 504" \ -l bunkerweb.INSTANCE \ bunkerity/bunkerweb:1.5.0-beta && \ docker network connect bw-universe bunkerweb @@ -294,7 +294,7 @@ Because the web UI is a web application, the recommended installation procedure -l "bunkerweb.REVERSE_PROXY_URL=/changeme" \ -l "bunkerweb.REVERSE_PROXY_HOST=http://bw-ui:7000" \ -l "bunkerweb.REVERSE_PROXY_HEADERS=X-Script-Name /changeme" \ - -l "bunkerweb.INTERCEPTED_ERROR_CODES=400 401.5.0-beta 405 413 429 500 501 502 503 504" \ + -l "bunkerweb.INTERCEPTED_ERROR_CODES=400 401 405 405 413 429 500 501 502 503 504" \ bunkerity/bunkerweb-ui:1.5.0-beta && \ docker network connect bw-docker bw-ui ``` @@ -379,7 +379,7 @@ Because the web UI is a web application, the recommended installation procedure - "bunkerweb.REVERSE_PROXY_URL=/changeme" - "bunkerweb.REVERSE_PROXY_HOST=http://bw-ui:7000" - "bunkerweb.REVERSE_PROXY_HEADERS=X-Script-Name /changeme" - - "bunkerweb.INTERCEPTED_ERROR_CODES=400 401.5.0-beta 405 413 429 500 501 502 503 504" + - "bunkerweb.INTERCEPTED_ERROR_CODES=400 401 405 405 413 429 500 501 502 503 504" volumes: bw-data: @@ -526,7 +526,7 @@ Because the web UI is a web application, the recommended installation procedure -l "bunkerweb.REVERSE_PROXY_URL=/changeme" \ -l "bunkerweb.REVERSE_PROXY_HOST=http://bw-ui:7000" \ -l "bunkerweb.REVERSE_PROXY_HEADERS=X-Script-Name /changeme" \ - -l "bunkerweb.INTERCEPTED_ERROR_CODES=400 401.5.0-beta 405 413 429 500 501 502 503 504" \ + -l "bunkerweb.INTERCEPTED_ERROR_CODES=400 401 405 405 413 429 500 501 502 503 504" \ bunkerity/bunkerweb-ui:1.5.0-beta ```