Elgato_dark/bunkerweb
1
0
Fork 0
mirror of https://github.com/bunkerity/bunkerweb synced 2026-04-21 13:37:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Road to 1.6.9 🚀

Browse source
This commit is contained in:
TheophileDiot 2026-03-13 17:36:39 +01:00
parent 83ed0952d9
commit 28b124740d
No known key found for this signature in database
GPG key ID: 7C44E4D7742628F8
149 changed files with 1060 additions and 1060 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/ISSUE_TEMPLATE/bug_report.yml vendored
View file

@ -51,7 +51,7 @@ body:
label: BunkerWeb version
description: What version of BunkerWeb are you running?
placeholder: Version
value: 1.6.9~rc4
value: 1.6.9
validations:
required: true
- type: dropdown

86
README.md
View file

@ -1,5 +1,5 @@
<p align="center">
<img alt="BunkerWeb logo" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/misc/logo.png" height=100 width=350 />
<img alt="BunkerWeb logo" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/misc/logo.png" height=100 width=350 />
</p>
<p align="center">
@ -32,7 +32,7 @@
&#124;
🧩 <a href="https://github.com/bunkerity/bunkerweb-templates">Templates</a>
&#124;
🛡️ <a href="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/examples">Examples</a>
🛡️ <a href="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/examples">Examples</a>
<br/>
💬 <a href="https://discord.com/invite/fTf46FmtyD">Chat</a>
&#124;
@ -52,14 +52,14 @@
# BunkerWeb
<p align="center">
<img alt="Overview banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/intro-overview.svg" />
<img alt="Overview banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/intro-overview.svg" />
</p>
BunkerWeb is a next-generation, open-source Web Application Firewall (WAF).
Being a full-featured web server (based on [NGINX](https://nginx.org/) under the hood), it will protect your web services to make them "secure by default." BunkerWeb integrates seamlessly into your existing environments ([Linux](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#linux), [Docker](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker), [Swarm](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#swarm), [Kubernetes](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#kubernetes), …) as a reverse proxy and is fully configurable (don't panic, there is an [awesome web UI](https://docs.bunkerweb.io/1.6.9~rc4/web-ui/?utm_campaign=self&utm_source=github) if you don't like the CLI) to meet your own use cases. In other words, cybersecurity is no longer a hassle.
Being a full-featured web server (based on [NGINX](https://nginx.org/) under the hood), it will protect your web services to make them "secure by default." BunkerWeb integrates seamlessly into your existing environments ([Linux](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#linux), [Docker](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker), [Swarm](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#swarm), [Kubernetes](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#kubernetes), …) as a reverse proxy and is fully configurable (don't panic, there is an [awesome web UI](https://docs.bunkerweb.io/1.6.9/web-ui/?utm_campaign=self&utm_source=github) if you don't like the CLI) to meet your own use cases. In other words, cybersecurity is no longer a hassle.
BunkerWeb contains primary [security features](https://docs.bunkerweb.io/1.6.9~rc4/advanced/?utm_campaign=self&utm_source=github#security-tuning) as part of the core but can be easily extended with additional ones thanks to a [plugin system](https://docs.bunkerweb.io/1.6.9~rc4/plugins/?utm_campaign=self&utm_source=github).
BunkerWeb contains primary [security features](https://docs.bunkerweb.io/1.6.9/advanced/?utm_campaign=self&utm_source=github#security-tuning) as part of the core but can be easily extended with additional ones thanks to a [plugin system](https://docs.bunkerweb.io/1.6.9/plugins/?utm_campaign=self&utm_source=github).
## Why BunkerWeb?
@ -86,7 +86,7 @@ A non-exhaustive list of security features:
- **Block known bad IPs** with external blacklists and DNSBL
- And much more...
Learn more about the core security features in the [security tuning](https://docs.bunkerweb.io/1.6.9~rc4/advanced/?utm_campaign=self&utm_source=github#security-tuning) section of the documentation.
Learn more about the core security features in the [security tuning](https://docs.bunkerweb.io/1.6.9/advanced/?utm_campaign=self&utm_source=github#security-tuning) section of the documentation.
## Demo
@ -121,13 +121,13 @@ When using BunkerWeb, you have the choice of the version you want to use: open-s
Whether it's enhanced security, an enriched user experience, or technical monitoring, the BunkerWeb PRO version allows you to fully benefit from BunkerWeb and meet your professional needs.
In the documentation or the user interface, PRO features are annotated with a crown <img src="https://docs.bunkerweb.io/1.6.9~rc4/assets/img/pro-icon.svg" alt="crown pro icon" height="32px" width="32px"> to distinguish them from those integrated into the open-source version.
In the documentation or the user interface, PRO features are annotated with a crown <img src="https://docs.bunkerweb.io/1.6.9/assets/img/pro-icon.svg" alt="crown pro icon" height="32px" width="32px"> to distinguish them from those integrated into the open-source version.
You can upgrade from the open-source version to the PRO one easily and at any time. The process is straightforward:
- Claim your [free trial on the BunkerWeb panel](https://panel.bunkerweb.io/store/bunkerweb-pro?utm_campaign=self&utm_source=doc) by using the `freetrial` promo code at checkout
- Once connected to the client area, copy your PRO license key
- Paste your license key into BunkerWeb using the [web UI](https://docs.bunkerweb.io/1.6.9~rc4/web-ui/#upgrade-to-pro) or a [specific setting](https://docs.bunkerweb.io/1.6.9~rc4/features/#pro)
- Paste your license key into BunkerWeb using the [web UI](https://docs.bunkerweb.io/1.6.9/web-ui/#upgrade-to-pro) or a [specific setting](https://docs.bunkerweb.io/1.6.9/features/#pro)
Do not hesitate to visit the [BunkerWeb panel](https://panel.bunkerweb.io/knowledgebase?utm_campaign=self&utm_source=doc) or [contact us](https://panel.bunkerweb.io/contact.php?utm_campaign=self&utm_source=doc) if you have any questions regarding the PRO version.
@ -160,10 +160,10 @@ Community and social networks:
# Concepts
<p align="center">
<img alt="Concepts banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/concepts.svg" />
<img alt="Concepts banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/concepts.svg" />
</p>
You will find more information about the key concepts of BunkerWeb in the [documentation](https://docs.bunkerweb.io/1.6.9~rc4/concepts/?utm_campaign=self&utm_source=github).
You will find more information about the key concepts of BunkerWeb in the [documentation](https://docs.bunkerweb.io/1.6.9/concepts/?utm_campaign=self&utm_source=github).
## Integrations
@ -171,12 +171,12 @@ The first concept is the integration of BunkerWeb into the target environment. W
The following integrations are officially supported:
- [Docker](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker)
- [Linux](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#linux)
- [Docker autoconf](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker-autoconf)
- [Kubernetes](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#kubernetes)
- [Swarm](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#swarm)
- [Microsoft Azure](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#microsoft-azure)
- [Docker](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker)
- [Linux](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#linux)
- [Docker autoconf](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker-autoconf)
- [Kubernetes](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#kubernetes)
- [Swarm](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#swarm)
- [Microsoft Azure](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#microsoft-azure)
## Settings
@ -206,7 +206,7 @@ When multisite mode is enabled, BunkerWeb will serve and protect multiple web ap
## Custom configurations
Because meeting all the use cases only using the settings is not an option (even with [external plugins](https://docs.bunkerweb.io/1.6.9~rc4/plugins/?utm_campaign=self&utm_source=github)), you can use custom configurations to solve your specific challenges.
Because meeting all the use cases only using the settings is not an option (even with [external plugins](https://docs.bunkerweb.io/1.6.9/plugins/?utm_campaign=self&utm_source=github)), you can use custom configurations to solve your specific challenges.
Under the hood, BunkerWeb uses the notorious NGINX web server, that's why you can leverage its configuration system for your specific needs. Custom NGINX configurations can be included in different [contexts](https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/#contexts) like HTTP or server (all servers and/or specific server block).
@ -215,7 +215,7 @@ Another core component of BunkerWeb is the ModSecurity Web Application Firewall:
## Database
<p align="center">
<img alt="Database model" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/bunkerweb_db.svg" />
<img alt="Database model" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/bunkerweb_db.svg" />
</p>
The state of the current configuration of BunkerWeb is stored in a backend database which contains the following data:
@ -244,7 +244,7 @@ In other words, the scheduler is the brain of BunkerWeb.
<!--## BunkerWeb Cloud
<p align="center">
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/bunkerweb-cloud.webp" />
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/bunkerweb-cloud.webp" />
</p>
BunkerWeb Cloud is the easiest way to get started with BunkerWeb. It offers you a fully managed BunkerWeb service with no hassle. Think of it like a BunkerWeb-as-a-Service!
@ -254,7 +254,7 @@ You will find more information about BunkerWeb Cloud beta [here](https://www.bun
## Linux
<p align="center">
<img alt="Linux banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-linux.svg" />
<img alt="Linux banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-linux.svg" />
</p>
List of supported Linux distros:
@ -274,7 +274,7 @@ You will find more information in the [Linux section](https://docs.bunkerweb.io/
## Docker
<p align="center">
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-docker.svg" />
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-docker.svg" />
</p>
We provide ready-to-use prebuilt images for x64, x86, armv7, and arm64 platforms on [Docker Hub](https://hub.docker.com/u/bunkerity).
@ -285,63 +285,63 @@ Docker integration key concepts are:
- **Scheduler** container to store configuration and execute jobs
- **Networks** to expose ports for clients and connect to upstream web services
You will find more information in the [Docker integration section](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker) of the documentation.
You will find more information in the [Docker integration section](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker) of the documentation.
## Docker autoconf
<p align="center">
<img alt="Docker autoconf banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-autoconf.svg" />
<img alt="Docker autoconf banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-autoconf.svg" />
</p>
The downside of using environment variables is that the container needs to be recreated each time there is an update, which is not very convenient. To counter that issue, you can use another image called **autoconf** which will listen for Docker events and automatically reconfigure BunkerWeb in real-time without recreating the container.
Instead of defining environment variables for the BunkerWeb container, you simply add **labels** to your web applications containers and the **autoconf** will "automagically" take care of the rest.
You will find more information in the [Docker autoconf section](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker-autoconf) of the documentation.
You will find more information in the [Docker autoconf section](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker-autoconf) of the documentation.
## Kubernetes
<p align="center">
<img alt="Kubernetes banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-kubernetes.svg" />
<img alt="Kubernetes banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-kubernetes.svg" />
</p>
The autoconf acts as an [Ingress controller](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/) and will configure the BunkerWeb instances according to the [Ingress resources](https://kubernetes.io/docs/concepts/services-networking/ingress/). It also monitors other Kubernetes objects like [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) for custom configurations.
The official [Helm chart](https://helm.sh/) for BunkerWeb is available in the [bunkerity/bunkerweb-helm repository](https://github.com/bunkerity/bunkerweb-helm).
You will find more information in the [Kubernetes section](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#kubernetes) of the documentation.
You will find more information in the [Kubernetes section](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#kubernetes) of the documentation.
## Microsoft Azure
<p align="center">
<img alt="Azure banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-azure.webp" />
<img alt="Azure banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-azure.webp" />
</p>
BunkerWeb is referenced in the [Azure Marketplace](https://azuremarketplace.microsoft.com/fr-fr/marketplace/apps/bunkerity.bunkerweb?tab=Overview) and an ARM template is available in the [misc folder](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/misc/integrations/azure-arm-template.json).
BunkerWeb is referenced in the [Azure Marketplace](https://azuremarketplace.microsoft.com/fr-fr/marketplace/apps/bunkerity.bunkerweb?tab=Overview) and an ARM template is available in the [misc folder](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/misc/integrations/azure-arm-template.json).
You will find more information in the [Microsoft Azure section](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#microsoft-azure) of the documentation.
You will find more information in the [Microsoft Azure section](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#microsoft-azure) of the documentation.
## Swarm
<p align="center">
<img alt="Swarm banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/docs/assets/img/integration-swarm.svg" />
<img alt="Swarm banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.9/docs/assets/img/integration-swarm.svg" />
</p>
To automatically configure BunkerWeb instances, a special service, called **autoconf** will listen for Docker Swarm events like service creation or deletion and automatically configure the **BunkerWeb instances** in real-time without downtime.
Like the [Docker autoconf integration](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#docker-autoconf), configuration for web services is defined using labels starting with the special **bunkerweb.** prefix.
Like the [Docker autoconf integration](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#docker-autoconf), configuration for web services is defined using labels starting with the special **bunkerweb.** prefix.
You will find more information in the [Swarm section](https://docs.bunkerweb.io/1.6.9~rc4/integrations/?utm_campaign=self&utm_source=github#swarm) of the documentation.
You will find more information in the [Swarm section](https://docs.bunkerweb.io/1.6.9/integrations/?utm_campaign=self&utm_source=github#swarm) of the documentation.
# Quickstart guide
Once you have set up BunkerWeb with the integration of your choice, you can follow the [quickstart guide](https://docs.bunkerweb.io/1.6.9~rc4/quickstart-guide/?utm_campaign=self&utm_source=github) that will cover the installation and first configuration to protect a web service.
Once you have set up BunkerWeb with the integration of your choice, you can follow the [quickstart guide](https://docs.bunkerweb.io/1.6.9/quickstart-guide/?utm_campaign=self&utm_source=github) that will cover the installation and first configuration to protect a web service.
# Security tuning
BunkerWeb offers many security features that you can configure with [features](https://docs.bunkerweb.io/1.6.9~rc4/features/?utm_campaign=self&utm_source=github). Even if the default values of settings ensure a minimal "security by default," we strongly recommend you to tune them. By doing so, you will be able to ensure a security level of your choice but also manage false positives.
BunkerWeb offers many security features that you can configure with [features](https://docs.bunkerweb.io/1.6.9/features/?utm_campaign=self&utm_source=github). Even if the default values of settings ensure a minimal "security by default," we strongly recommend you to tune them. By doing so, you will be able to ensure a security level of your choice but also manage false positives.
You will find more information in the [security tuning section](https://docs.bunkerweb.io/1.6.9~rc4/advanced/?utm_campaign=self&utm_source=github#security-tuning) of the documentation.
You will find more information in the [security tuning section](https://docs.bunkerweb.io/1.6.9/advanced/?utm_campaign=self&utm_source=github#security-tuning) of the documentation.
# Settings
@ -349,7 +349,7 @@ As a general rule, when multisite mode is enabled, if you want to apply settings
When settings are considered as "multiple," it means that you can have multiple groups of settings for the same feature by adding numbers as suffixes like `REVERSE_PROXY_URL_1=/subdir`, `REVERSE_PROXY_HOST_1=http://myhost1`, `REVERSE_PROXY_URL_2=/anotherdir`, `REVERSE_PROXY_HOST_2=http://myhost2`, ... for example.
Check the [features section](https://docs.bunkerweb.io/1.6.9~rc4/features/?utm_campaign=self&utm_source=github) of the documentation to get the full list.
Check the [features section](https://docs.bunkerweb.io/1.6.9/features/?utm_campaign=self&utm_source=github) of the documentation to get the full list.
# Web UI
@ -368,7 +368,7 @@ Here is the list of features offered by the web UI:
- Monitor job execution and restart them when needed
- View the logs and search patterns
You will find more information in the [Web UI section](https://docs.bunkerweb.io/1.6.9~rc4/web-ui/?utm_campaign=self&utm_source=github) of the documentation.
You will find more information in the [Web UI section](https://docs.bunkerweb.io/1.6.9/web-ui/?utm_campaign=self&utm_source=github) of the documentation.
# Plugins
@ -385,7 +385,7 @@ Here is the list of "official" plugins that we maintain (see the [bunkerweb-plug
| **VirusTotal** | 1.9 | Automatically scans uploaded files with the VirusTotal API and denies the request when a file is detected as malicious. | [bunkerweb-plugins/virustotal](https://github.com/bunkerity/bunkerweb-plugins/tree/main/virustotal) |
| **WebHook** | 1.9 | Send security notifications to a custom HTTP endpoint using a Webhook. | [bunkerweb-plugins/webhook](https://github.com/bunkerity/bunkerweb-plugins/tree/main/webhook) |
You will find more information in the [plugins section](https://docs.bunkerweb.io/1.6.9~rc4/plugins/?utm_campaign=self&utm_source=github) of the documentation.
You will find more information in the [plugins section](https://docs.bunkerweb.io/1.6.9/plugins/?utm_campaign=self&utm_source=github) of the documentation.
# Language Support & Localization
@ -409,7 +409,7 @@ BunkerWeb UI supports multiple languages. Translations are managed in the `src/u
- Urdu (ur)
- Simplified Chinese (zh)
See the [locales/README.md](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/src/ui/app/static/locales/README.md) for details on translation provenance and review status.
See the [locales/README.md](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/src/ui/app/static/locales/README.md) for details on translation provenance and review status.
## Contributing Translations
@ -425,7 +425,7 @@ We welcome contributions to improve or add new locale files!
For updates, edit the relevant file and update the provenance table as needed.
See the [locales/README.md](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/src/ui/app/static/locales/README.md) for full guidelines.
See the [locales/README.md](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/src/ui/app/static/locales/README.md) for full guidelines.
# Support
@ -448,15 +448,15 @@ Please don't use [GitHub issues](https://github.com/bunkerity/bunkerweb/issues)
# License
This project is licensed under the terms of the [GNU Affero General Public License (AGPL) version 3](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/LICENSE.md).
This project is licensed under the terms of the [GNU Affero General Public License (AGPL) version 3](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/LICENSE.md).
# Contribute
If you would like to contribute to the plugins, you can read the [contributing guidelines](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/CONTRIBUTING.md) to get started.
If you would like to contribute to the plugins, you can read the [contributing guidelines](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/CONTRIBUTING.md) to get started.
# Security policy
We take security bugs as serious issues and encourage responsible disclosure; see our [security policy](https://github.com/bunkerity/bunkerweb/raw/v1.6.9-rc4/SECURITY.md) for more information.
We take security bugs as serious issues and encourage responsible disclosure; see our [security policy](https://github.com/bunkerity/bunkerweb/raw/v1.6.9/SECURITY.md) for more information.
# Star History

106
docs/advanced.md
View file

@ -1,8 +1,8 @@
# Advanced usages
Many real-world use case examples are available in the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) folder of the GitHub repository.
Many real-world use case examples are available in the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) folder of the GitHub repository.
We also provide numerous boilerplates, such as YAML files for various integrations and database types. These are available in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) folder.
We also provide numerous boilerplates, such as YAML files for various integrations and database types. These are available in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) folder.
This section only focuses on advanced usages and security tuning, see the [features section](features.md) of the documentation to see all the available settings.
@ -85,7 +85,7 @@ You will find more settings about real IP in the [features section](features.md#
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Please note that if your container is already created, you will need to delete it and recreate it so the new environment variables will be updated.
@ -96,7 +96,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -104,7 +104,7 @@ You will find more settings about real IP in the [features section](features.md#
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -121,7 +121,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -129,7 +129,7 @@ You will find more settings about real IP in the [features section](features.md#
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -176,7 +176,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -184,7 +184,7 @@ You will find more settings about real IP in the [features section](features.md#
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -249,7 +249,7 @@ You will find more settings about real IP in the [features section](features.md#
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Please note that if your container is already created, you will need to delete it and recreate it so the new environment variables will be updated.
@ -260,7 +260,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -270,7 +270,7 @@ You will find more settings about real IP in the [features section](features.md#
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -288,7 +288,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -298,7 +298,7 @@ You will find more settings about real IP in the [features section](features.md#
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -350,7 +350,7 @@ You will find more settings about real IP in the [features section](features.md#
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -360,7 +360,7 @@ You will find more settings about real IP in the [features section](features.md#
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -485,8 +485,8 @@ The Manager is the brain of the cluster. It runs the Scheduler, Database, and op
```bash
# Download script and checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -585,7 +585,7 @@ The Manager is the brain of the cluster. It runs the Scheduler, Database, and op
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: "192.168.1.11 192.168.1.12" # Replace with your worker IPs
@ -604,7 +604,7 @@ The Manager is the brain of the cluster. It runs the Scheduler, Database, and op
- bw-redis
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
ports:
- "7000:7000" # Expose the Web UI port
environment:
@ -687,7 +687,7 @@ Workers are the nodes that process incoming traffic.
```yaml title="docker-compose.yml"
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -992,7 +992,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1020,7 +1020,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
- bw-dns
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1031,7 +1031,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
- bw-dns
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1145,7 +1145,7 @@ Some integrations provide more convenient ways to apply configurations, such as
}" \
-p 80:8080/tcp \
-p 443:8443/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@ -1185,7 +1185,7 @@ Some integrations provide more convenient ways to apply configurations, such as
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1208,7 +1208,7 @@ Some integrations provide more convenient ways to apply configurations, such as
```yaml
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- |
CUSTOM_CONF_SERVER_HTTP_hello-world=
@ -1251,7 +1251,7 @@ Some integrations provide more convenient ways to apply configurations, such as
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1321,7 +1321,7 @@ Some integrations provide more convenient ways to apply configurations, such as
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1551,7 +1551,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
-p 443:8443/udp \
-p 10000:10000/tcp \
-p 20000:20000/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@ -1574,7 +1574,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
- "10000:10000" # app1
@ -1589,7 +1589,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -1640,7 +1640,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
- "10000:10000" # app1
@ -1870,7 +1870,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
# Keep it if you want to use Let's Encrypt automation when using http challenge type
- published: 80
@ -2000,7 +2000,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@ -2044,7 +2044,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2059,7 +2059,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -2153,7 +2153,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
environment:
@ -2166,7 +2166,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -2181,7 +2181,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2421,7 +2421,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
volumes:
- /shared/www:/var/www/html
...
@ -2520,7 +2520,7 @@ By default, BunkerWeb will only listen on IPv4 addresses and won't use IPv6 for
```yaml
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
USE_IPv6: "yes"
@ -2660,7 +2660,7 @@ LOG_LEVEL_1=error
services:
bunkerweb:
# This is the name that will be used to identify the instance in the Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2673,7 +2673,7 @@ LOG_LEVEL_1=error
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
@ -2690,7 +2690,7 @@ LOG_LEVEL_1=error
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
volumes:
@ -2825,7 +2825,7 @@ You can configure the logging driver for your services in your `docker-compose.y
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
logging:
driver: "json-file"
options:
@ -2934,7 +2934,7 @@ The commonly used variables are:
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
If the container already exists, recreate it to apply the new environment.
@ -2945,7 +2945,7 @@ The commonly used variables are:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -2964,7 +2964,7 @@ The commonly used variables are:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3007,7 +3007,7 @@ The commonly used variables are:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3959,11 +3959,11 @@ Templates use Lua template syntax with the following delimiters:
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
# ... other settings (no environment variables needed here for custom pages)
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./templates:/custom_templates:ro
environment:
@ -4046,7 +4046,7 @@ Templates use Lua template syntax with the following delimiters:
spec:
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
env:
- name: CUSTOM_ERROR_PAGE
value: "/custom_templates/error.html"

8
docs/api.md
View file

@ -41,7 +41,7 @@ Choose the flavor that matches your environment.
services:
bunkerweb:
# This is the name that will be used to identify the instance in the Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -54,7 +54,7 @@ Choose the flavor that matches your environment.
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
@ -76,7 +76,7 @@ Choose the flavor that matches your environment.
- bw-db
bw-api:
image: bunkerity/bunkerweb-api:1.6.9-rc4
image: bunkerity/bunkerweb-api:1.6.9
environment:
<<: *bw-env
API_USERNAME: "admin"
@ -143,7 +143,7 @@ Choose the flavor that matches your environment.
-e SERVICE_API=yes \
-e API_WHITELIST_IPS="127.0.0.0/8" \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Linux"

4
docs/concepts.md
View file

@ -105,7 +105,7 @@ Please note that multisite mode is implicit when using the web User Interface. Y
!!! info "Going further"
You will find concrete examples of multisite mode in the [advanced usages](advanced.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) directory of the repository.
You will find concrete examples of multisite mode in the [advanced usages](advanced.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) directory of the repository.
## Custom configurations {#custom-configurations}
@ -126,7 +126,7 @@ Managing custom configurations from the web User Interface is done through the *
!!! info "Going further"
You will find concrete examples of custom configurations in the [advanced usages](advanced.md#custom-configurations) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) directory of the repository.
You will find concrete examples of custom configurations in the [advanced usages](advanced.md#custom-configurations) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) directory of the repository.
## Database

106
docs/de/advanced.md
View file

@ -1,8 +1,8 @@
# Fortgeschrittene Nutzungen
Viele Beispiele für reale Anwendungsfälle sind im Ordner [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) des GitHub-Repositorys verfügbar.
Viele Beispiele für reale Anwendungsfälle sind im Ordner [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) des GitHub-Repositorys verfügbar.
Wir stellen auch zahlreiche Boilerplates zur Verfügung, wie z. B. YAML-Dateien für verschiedene Integrationen und Datenbanktypen. Diese sind im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) verfügbar.
Wir stellen auch zahlreiche Boilerplates zur Verfügung, wie z. B. YAML-Dateien für verschiedene Integrationen und Datenbanktypen. Diese sind im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) verfügbar.
Dieser Abschnitt konzentriert sich nur auf fortgeschrittene Nutzungen und Sicherheits-Tuning. Informationen zu allen verfügbaren Einstellungen finden Sie im [Features-Abschnitt](features.md) der Dokumentation.
@ -85,7 +85,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Bitte beachten Sie, dass Sie, wenn Ihr Container bereits erstellt wurde, ihn löschen und neu erstellen müssen, damit die neuen Umgebungsvariablen aktualisiert werden.
@ -96,7 +96,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -104,7 +104,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -121,7 +121,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -129,7 +129,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -176,7 +176,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -184,7 +184,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -249,7 +249,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Bitte beachten Sie, dass Sie, wenn Ihr Container bereits erstellt wurde, ihn löschen und neu erstellen müssen, damit die neuen Umgebungsvariablen aktualisiert werden.
@ -260,7 +260,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -270,7 +270,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -288,7 +288,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -298,7 +298,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -350,7 +350,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -360,7 +360,7 @@ Weitere Einstellungen zur echten IP finden Sie im [Features-Abschnitt](features.
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -485,8 +485,8 @@ Der Manager ist das Gehirn des Clusters. Er führt den Scheduler, die Datenbank
```bash
# Skript und Checksumme laden
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Prüfsumme verifizieren
sha256sum -c install-bunkerweb.sh.sha256
@ -585,7 +585,7 @@ Der Manager ist das Gehirn des Clusters. Er führt den Scheduler, die Datenbank
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: "192.168.1.11 192.168.1.12" # Ersetzen durch die IPs Ihrer Worker
@ -604,7 +604,7 @@ Der Manager ist das Gehirn des Clusters. Er führt den Scheduler, die Datenbank
- bw-redis
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
ports:
- "7000:7000" # UI-Port veröffentlichen
environment:
@ -687,7 +687,7 @@ Worker sind die Knoten, die den eingehenden Verkehr verarbeiten.
```yaml title="docker-compose.yml"
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -992,7 +992,7 @@ Um systemd-resolved als Ihren DNS-Resolver in BunkerWeb zu aktivieren, setzen Si
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1020,7 +1020,7 @@ Um systemd-resolved als Ihren DNS-Resolver in BunkerWeb zu aktivieren, setzen Si
- bw-dns
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1031,7 +1031,7 @@ Um systemd-resolved als Ihren DNS-Resolver in BunkerWeb zu aktivieren, setzen Si
- bw-dns
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1145,7 +1145,7 @@ Einige Integrationen bieten bequemere Möglichkeiten zum Anwenden von Konfigurat
}" \
-p 80:8080/tcp \
-p 443:8443/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Bitte beachten Sie, dass Sie, wenn Ihr Container bereits erstellt wurde, ihn löschen und neu erstellen müssen, damit die neuen Umgebungsvariablen angewendet werden.
@ -1185,7 +1185,7 @@ Einige Integrationen bieten bequemere Möglichkeiten zum Anwenden von Konfigurat
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1208,7 +1208,7 @@ Einige Integrationen bieten bequemere Möglichkeiten zum Anwenden von Konfigurat
```yaml
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- |
CUSTOM_CONF_SERVER_HTTP_hello-world=
@ -1251,7 +1251,7 @@ Einige Integrationen bieten bequemere Möglichkeiten zum Anwenden von Konfigurat
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1321,7 +1321,7 @@ Einige Integrationen bieten bequemere Möglichkeiten zum Anwenden von Konfigurat
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1552,7 +1552,7 @@ Eine vollständige Liste der Einstellungen für den `stream`-Modus finden Sie im
-p 443:8443/udp \
-p 10000:10000/tcp \
-p 20000:20000/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Bitte beachten Sie, dass Sie, wenn Ihr Container bereits erstellt wurde, ihn löschen und neu erstellen müssen, damit die neuen Umgebungsvariablen angewendet werden.
@ -1575,7 +1575,7 @@ Eine vollständige Liste der Einstellungen für den `stream`-Modus finden Sie im
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Behalten, wenn Sie die Let's Encrypt-Automatisierung mit dem http-Challenge-Typ verwenden möchten
- "10000:10000" # app1
@ -1590,7 +1590,7 @@ Eine vollständige Liste der Einstellungen für den `stream`-Modus finden Sie im
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Diese Einstellung ist obligatorisch, um die BunkerWeb-Instanz anzugeben
@ -1641,7 +1641,7 @@ Eine vollständige Liste der Einstellungen für den `stream`-Modus finden Sie im
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Behalten, wenn Sie die Let's Encrypt-Automatisierung mit dem http-Challenge-Typ verwenden möchten
- "10000:10000" # app1
@ -1871,7 +1871,7 @@ Eine vollständige Liste der Einstellungen für den `stream`-Modus finden Sie im
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
# Behalten, wenn Sie die Let's Encrypt-Automatisierung mit dem http-Challenge-Typ verwenden möchten
- published: 80
@ -2001,7 +2001,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Bitte beachten Sie, dass Sie, wenn Ihr Container bereits erstellt wurde, ihn löschen und neu erstellen müssen, damit die neuen Umgebungsvariablen angewendet werden.
@ -2045,7 +2045,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2060,7 +2060,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Diese Einstellung ist obligatorisch, um die BunkerWeb-Instanz anzugeben
@ -2154,7 +2154,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
environment:
@ -2167,7 +2167,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "" # Wir müssen die BunkerWeb-Instanz hier nicht angeben, da sie automatisch vom Autoconf-Dienst erkannt werden
@ -2182,7 +2182,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2422,7 +2422,7 @@ BunkerWeb unterstützt PHP über externe oder entfernte [PHP-FPM](https://www.ph
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
volumes:
- /shared/www:/var/www/html
...
@ -2521,7 +2521,7 @@ Standardmäßig lauscht BunkerWeb nur auf IPv4-Adressen und verwendet kein IPv6
```yaml
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
USE_IPv6: "yes"
@ -2661,7 +2661,7 @@ LOG_LEVEL_1=error
services:
bunkerweb:
# Dies ist der Name, der zur Identifikation der Instanz im Scheduler verwendet wird
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2674,7 +2674,7 @@ LOG_LEVEL_1=error
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Stellen Sie sicher, dass Sie den richtigen Instanznamen setzen
@ -2691,7 +2691,7 @@ LOG_LEVEL_1=error
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
volumes:
@ -2826,7 +2826,7 @@ Sie können den Protokollierungstreiber für Ihre Dienste in Ihrer `docker-compo
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
logging:
driver: "json-file"
options:
@ -2935,7 +2935,7 @@ Die üblichen Variablen sind:
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Wenn der Container bereits existiert, erstellen Sie ihn neu, um die neue Umgebung anzuwenden.
@ -2946,7 +2946,7 @@ Die üblichen Variablen sind:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -2965,7 +2965,7 @@ Die üblichen Variablen sind:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3008,7 +3008,7 @@ Die üblichen Variablen sind:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3960,11 +3960,11 @@ Vorlagen verwenden Lua-Vorlagensyntax mit den folgenden Trennzeichen:
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
# ... andere Einstellungen (keine Umgebungsvariablen für Custom Pages hier benötigt)
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./templates:/custom_templates:ro
environment:
@ -4047,7 +4047,7 @@ Vorlagen verwenden Lua-Vorlagensyntax mit den folgenden Trennzeichen:
spec:
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
env:
- name: CUSTOM_ERROR_PAGE
value: "/custom_templates/error.html"

8
docs/de/api.md
View file

@ -41,7 +41,7 @@ Wählen Sie die Variante, die zu Ihrer Umgebung passt.
services:
bunkerweb:
# Name, unter dem die Instanz im Scheduler erscheint
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -54,7 +54,7 @@ Wählen Sie die Variante, die zu Ihrer Umgebung passt.
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Instanznamen korrekt setzen
@ -76,7 +76,7 @@ Wählen Sie die Variante, die zu Ihrer Umgebung passt.
- bw-db
bw-api:
image: bunkerity/bunkerweb-api:1.6.9-rc4
image: bunkerity/bunkerweb-api:1.6.9
environment:
<<: *bw-env
API_USERNAME: "admin"
@ -143,7 +143,7 @@ Wählen Sie die Variante, die zu Ihrer Umgebung passt.
-e SERVICE_API=yes \
-e API_WHITELIST_IPS="127.0.0.0/8" \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Linux"

4
docs/de/concepts.md
View file

@ -105,7 +105,7 @@ Bitte beachten Sie, dass der Multisite-Modus bei Verwendung der Web-Benutzerober
!!! info "Weiterführende Informationen"
Konkrete Beispiele für den Multisite-Modus finden Sie in den [fortgeschrittenen Nutzungen](advanced.md) der Dokumentation und im [Beispiele](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples)-Verzeichnis des Repositorys.
Konkrete Beispiele für den Multisite-Modus finden Sie in den [fortgeschrittenen Nutzungen](advanced.md) der Dokumentation und im [Beispiele](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples)-Verzeichnis des Repositorys.
## Benutzerdefinierte Konfigurationen {#custom-configurations}
@ -126,7 +126,7 @@ Die Verwaltung benutzerdefinierter Konfigurationen über die Web-Benutzeroberfl
!!! info "Weiterführende Informationen"
Konkrete Beispiele für benutzerdefinierte Konfigurationen finden Sie in den [fortgeschrittenen Nutzungen](advanced.md#custom-configurations) der Dokumentation und im [Beispiele](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples)-Verzeichnis des Repositorys.
Konkrete Beispiele für benutzerdefinierte Konfigurationen finden Sie in den [fortgeschrittenen Nutzungen](advanced.md#custom-configurations) der Dokumentation und im [Beispiele](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples)-Verzeichnis des Repositorys.
## Datenbank

4
docs/de/features.md
View file

@ -1696,7 +1696,7 @@ Die folgenden Abschnitte führen diese Schritte im Detail durch.
services:
bunkerweb:
# Dies ist der Name, der zur Identifizierung der Instanz im Scheduler verwendet wird
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1713,7 +1713,7 @@ Die folgenden Abschnitte führen diese Schritte im Detail durch.
syslog-address: "udp://10.20.30.254:514" # Die IP-Adresse des syslog-Dienstes
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Stellen Sie sicher, dass Sie den richtigen Instanznamen festlegen

108
docs/de/integrations.md
View file

@ -1268,7 +1268,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Standardmäßig stellt der Container Folgendes bereit:
@ -1284,7 +1284,7 @@ Ein benanntes Volume (oder Bind-Mount) ist erforderlich, um die unter `/data` ge
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
volumes:
- bw-storage:/data
...
@ -1361,7 +1361,7 @@ docker run -d \
-e API_PASSWORD=StrongP@ssw0rd \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
-p 8888:8888/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Empfohlen (hinter BunkerWeb) — veröffentlichen Sie `8888` nicht; verwenden Sie stattdessen einen Reverse-Proxy:
@ -1369,7 +1369,7 @@ Empfohlen (hinter BunkerWeb) — veröffentlichen Sie `8888` nicht; verwenden Si
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1441,7 +1441,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4```
bunkerity/bunkerweb-all-in-one:1.6.9```
* Wenn `USE_CROWDSEC=yes`, wird das Einstiegsskript:
@ -1495,7 +1495,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
!!! info "Wie es intern funktioniert"
@ -1517,7 +1517,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Hinweise:
@ -1553,7 +1553,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* Die **lokale Registrierung** wird übersprungen, wenn `CROWDSEC_API` nicht `127.0.0.1` oder `localhost` ist.
@ -1585,13 +1585,13 @@ Um Ihre Docker-Bereitstellung zu erleichtern, stellen wir auf [Docker Hub](https
Durch den Zugriff auf diese vorgefertigten Images von Docker Hub können Sie BunkerWeb schnell in Ihrer Docker-Umgebung ziehen und ausführen, wodurch umfangreiche Konfigurations- oder Einrichtungsprozesse entfallen. Dieser optimierte Ansatz ermöglicht es Ihnen, sich auf die Nutzung der Funktionen von BunkerWeb zu konzentrieren, ohne unnötige Komplexität.
```shell
docker pull bunkerity/bunkerweb:1.6.9-rc4
docker pull bunkerity/bunkerweb:1.6.9
```
Docker-Images sind auch auf [GitHub-Paketen](https://github.com/orgs/bunkerity/packages?repo_name=bunkerweb) verfügbar und können über die Repository-Adresse `ghcr.io` heruntergeladen werden:
```shell
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9-rc4
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9
```
Schlüsselkonzepte für die Docker-Integration sind:
@ -1601,7 +1601,7 @@ Schlüsselkonzepte für die Docker-Integration sind:
- **Netzwerke**: Docker-Netzwerke spielen eine wichtige Rolle bei der Integration von BunkerWeb. Diese Netzwerke dienen zwei Hauptzwecken: dem Bereitstellen von Ports für Clients und dem Verbinden mit Upstream-Webdiensten. Durch das Bereitstellen von Ports kann BunkerWeb eingehende Anfragen von Clients annehmen und ihnen den Zugriff auf die geschützten Webdienste ermöglichen. Darüber hinaus kann BunkerWeb durch die Verbindung mit Upstream-Webdiensten den Datenverkehr effizient weiterleiten und verwalten und so eine verbesserte Sicherheit und Leistung bieten.
!!! info "Datenbank-Backend"
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie SQLite als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Es werden jedoch auch andere Datenbank-Backends unterstützt. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) des Repositorys.
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie SQLite als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Es werden jedoch auch andere Datenbank-Backends unterstützt. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) des Repositorys.
### Umgebungsvariablen
@ -1611,7 +1611,7 @@ Einstellungen werden dem Scheduler über Docker-Umgebungsvariablen übergeben:
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- MY_SETTING=value
- ANOTHER_SETTING=another value
@ -1655,7 +1655,7 @@ Dadurch wird sichergestellt, dass sensible Einstellungen aus der Umgebung und de
Der [Scheduler](concepts.md#scheduler) läuft in seinem eigenen Container, der auch auf Docker Hub verfügbar ist:
```shell
docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
docker pull bunkerity/bunkerweb-scheduler:1.6.9
```
!!! info "BunkerWeb-Einstellungen"
@ -1676,7 +1676,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
environment:
# Dies setzt die API-Einstellungen für den BunkerWeb-Container
<<: *bw-api-env
@ -1685,7 +1685,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
- bw-universe
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
# Dies setzt die API-Einstellungen für den Scheduler-Container
<<: *bw-api-env
@ -1703,7 +1703,7 @@ Ein Volume wird benötigt, um die vom Scheduler verwendete SQLite-Datenbank und
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- bw-storage:/data
...
@ -1849,7 +1849,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1862,7 +1862,7 @@ services:
- bw-universe
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Diese Einstellung ist obligatorisch, um die BunkerWeb-Instanz anzugeben
@ -1895,7 +1895,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1908,7 +1908,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
environment:
@ -1974,8 +1974,8 @@ Um zu beginnen, laden Sie das Installationsskript und seine Prüfsumme herunter
```bash
# Skript und Prüfsumme herunterladen
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Prüfsumme überprüfen
sha256sum -c install-bunkerweb.sh.sha256
@ -2034,7 +2034,7 @@ Für nicht-interaktive oder automatisierte Setups kann das Skript mit Befehlszei
| Option | Beschreibung |
| ----------------------- | ------------------------------------------------------------------------------------------- |
| `-v, --version VERSION` | Gibt die zu installierende BunkerWeb-Version an (z. B. `1.6.9~rc4`). |
| `-v, --version VERSION` | Gibt die zu installierende BunkerWeb-Version an (z. B. `1.6.9`). |
| `-w, --enable-wizard` | Aktiviert den Einrichtungsassistenten. |
| `-n, --no-wizard` | Deaktiviert den Einrichtungsassistenten. |
| `-y, --yes` | Führt im nicht-interaktiven Modus mit Standardantworten für alle Eingabeaufforderungen aus. |
@ -2099,7 +2099,7 @@ sudo ./install-bunkerweb.sh --yes
sudo ./install-bunkerweb.sh --worker --no-wizard
# Eine bestimmte Version installieren
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
sudo ./install-bunkerweb.sh --version 1.6.9
# Manager-Setup mit entfernten Worker-Instanzen (Instanzen erforderlich)
sudo ./install-bunkerweb.sh --manager --instances "192.168.1.10 192.168.1.11"
@ -2243,12 +2243,12 @@ Bitte stellen Sie sicher, dass Sie **NGINX 1.28.2 installiert haben, bevor Sie B
export UI_WIZARD=no
```
Und installieren Sie schließlich BunkerWeb 1.6.9~rc4:
Und installieren Sie schließlich BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Um ein Upgrade der NGINX- und/oder BunkerWeb-Pakete bei der Ausführung von `apt upgrade` zu verhindern, können Sie den folgenden Befehl verwenden:
@ -2291,12 +2291,12 @@ Bitte stellen Sie sicher, dass Sie **NGINX 1.28.2 installiert haben, bevor Sie B
export UI_WIZARD=no
```
Und installieren Sie schließlich BunkerWeb 1.6.9~rc4:
Und installieren Sie schließlich BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Um ein Upgrade der NGINX- und/oder BunkerWeb-Pakete bei der Ausführung von `apt upgrade` zu verhindern, können Sie den folgenden Befehl verwenden:
@ -2327,12 +2327,12 @@ Bitte stellen Sie sicher, dass Sie **NGINX 1.28.2 installiert haben, bevor Sie B
export UI_WIZARD=no
```
Und installieren Sie schließlich BunkerWeb 1.6.9~rc4:
Und installieren Sie schließlich BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf makecache && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Um ein Upgrade der NGINX- und/oder BunkerWeb-Pakete bei der Ausführung von `dnf upgrade` zu verhindern, können Sie den folgenden Befehl verwenden:
@ -2377,12 +2377,12 @@ Bitte stellen Sie sicher, dass Sie **NGINX 1.28.2 installiert haben, bevor Sie B
export UI_WIZARD=no
```
Und installieren Sie schließlich BunkerWeb 1.6.9~rc4:
Und installieren Sie schließlich BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Um ein Upgrade der NGINX- und/oder BunkerWeb-Pakete bei der Ausführung von `dnf upgrade` zu verhindern, können Sie den folgenden Befehl verwenden:
@ -2474,7 +2474,7 @@ Durch die Übernahme dieses Ansatzes können Sie eine Echtzeit-Rekonfiguration v
Die Docker Autoconf-Integration impliziert die Verwendung des **Multisite-Modus**. Weitere Informationen finden Sie im [Multisite-Abschnitt](concepts.md#multisite-mode) der Dokumentation.
!!! info "Datenbank-Backend"
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) des Repositorys.
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) des Repositorys.
Um automatisierte Konfigurationsupdates zu ermöglichen, fügen Sie einen zusätzlichen Container namens `bw-autoconf` zum Stack hinzu. Dieser Container hostet den Autoconf-Dienst, der dynamische Konfigurationsänderungen für BunkerWeb verwaltet.
@ -2488,7 +2488,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2503,7 +2503,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # Wir müssen die BunkerWeb-Instanz hier nicht angeben, da sie automatisch vom Autoconf-Dienst erkannt werden
@ -2518,7 +2518,7 @@ services:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2701,13 +2701,13 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
- "bunkerweb.NAMESPACE=my-namespace" # Setzen Sie den Namespace für die BunkerWeb-Instanz, damit der Autoconf-Dienst sie erkennen kann
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
...
NAMESPACES: "my-namespace my-other-namespace" # Lauschen Sie nur auf diese Namespaces
@ -2759,7 +2759,7 @@ Für eine optimale Einrichtung wird empfohlen, BunkerWeb als **[DaemonSet](https
Angesichts des Vorhandenseins mehrerer BunkerWeb-Instanzen ist es erforderlich, einen gemeinsamen Datenspeicher zu implementieren, der als [Redis](https://redis.io/)- oder [Valkey](https://valkey.io/)-Dienst realisiert wird. Dieser Dienst wird von den Instanzen genutzt, um Daten zwischen ihnen zu cachen und zu teilen. Weitere Informationen zu den Redis/Valkey-Einstellungen finden Sie [hier](features.md#redis).
!!! info "Datenbank-Backend"
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) des Repositorys.
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) des Repositorys.
Die Einrichtung von geclusterten Datenbank-Backends liegt außerhalb des Geltungsbereichs dieser Dokumentation.
@ -2874,7 +2874,7 @@ The **BunkerWeb controller** automatically discovers pods with BunkerWeb sidecar
```yaml
controller:
enabled: true
tag: "1.6.9~rc4"
tag: "1.6.9"
```
2. For each sidecar, add:
@ -2967,7 +2967,7 @@ In your BunkerWeb chart `values.yaml`, configure the `BUNKERWEB_INSTANCES` envir
```yaml
scheduler:
tag: "1.6.9~rc4"
tag: "1.6.9"
extraEnvs:
- name: BUNKERWEB_INSTANCES
value: "http://app1-bunkerweb-workers.namespace.svc.cluster.local:5000 http://app2-bunkerweb-workers.namespace.svc.cluster.local:5000"
@ -3011,7 +3011,7 @@ spec:
# BunkerWeb Sidecar
- name: bunkerweb
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- containerPort: 8080 # Exposed HTTP port
- containerPort: 5000 # Internal API (mandatory)
@ -3282,7 +3282,7 @@ To add a new application protected by BunkerWeb:
#### Vollständige YAML-Dateien
Anstatt das Helm-Chart zu verwenden, können Sie auch die YAML-Vorlagen im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) des GitHub-Repositorys verwenden. Bitte beachten Sie, dass wir dringend empfehlen, stattdessen das Helm-Chart zu verwenden.
Anstatt das Helm-Chart zu verwenden, können Sie auch die YAML-Vorlagen im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) des GitHub-Repositorys verwenden. Bitte beachten Sie, dass wir dringend empfehlen, stattdessen das Helm-Chart zu verwenden.
### Ingress-Ressourcen
@ -3430,7 +3430,7 @@ metadata:
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
imagePullPolicy: Always
env:
- name: NAMESPACES
@ -3604,11 +3604,11 @@ service:
# BunkerWeb-Einstellungen
bunkerweb:
tag: 1.6.9~rc4
tag: 1.6.9
# Scheduler-Einstellungen
scheduler:
tag: 1.6.9~rc4
tag: 1.6.9
extraEnvs:
# Aktivieren Sie das Real-IP-Modul, um die echte IP der Clients zu erhalten
- name: USE_REAL_IP
@ -3616,11 +3616,11 @@ scheduler:
# Controller-Einstellungen
controller:
tag: 1.6.9~rc4
tag: 1.6.9
# UI-Einstellungen
ui:
tag: 1.6.9~rc4
tag: 1.6.9
```
Installieren Sie BunkerWeb mit benutzerdefinierten Werten:
@ -4242,7 +4242,7 @@ Da mehrere Instanzen von BunkerWeb ausgeführt werden, muss ein gemeinsamer Date
Was das Datenbank-Volume betrifft, so gibt die Dokumentation keinen spezifischen Ansatz vor. Die Wahl eines freigegebenen Ordners oder eines bestimmten Treibers für das Datenbank-Volume hängt von Ihrem einzigartigen Anwendungsfall ab und bleibt dem Leser als Übung überlassen.
!!! info "Datenbank-Backend"
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) des Repositorys.
Bitte beachten Sie, dass unsere Anweisungen davon ausgehen, dass Sie MariaDB als Standard-Datenbank-Backend verwenden, wie durch die Einstellung `DATABASE_URI` konfiguriert. Wir verstehen jedoch, dass Sie möglicherweise alternative Backends für Ihre Docker-Integration bevorzugen. In diesem Fall können Sie sicher sein, dass auch andere Datenbank-Backends möglich sind. Weitere Informationen finden Sie in den docker-compose-Dateien im Ordner [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) des Repositorys.
Die Einrichtung von geclusterten Datenbank-Backends liegt außerhalb des Geltungsbereichs dieser Dokumentation.
@ -4256,7 +4256,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -4285,7 +4285,7 @@ services:
- "bunkerweb.INSTANCE=yes" # Obligatorisches Label für den Autoconf-Dienst, um die BunkerWeb-Instanz zu identifizieren
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # Wir müssen die BunkerWeb-Instanz hier nicht angeben, da sie automatisch vom Autoconf-Dienst erkannt werden
@ -4306,7 +4306,7 @@ services:
- "node.role == worker"
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
SWARM_MODE: "yes"
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Denken Sie daran, ein stärkeres Passwort für die Datenbank festzulegen
@ -4458,7 +4458,7 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
deploy:
mode: global
@ -4470,7 +4470,7 @@ networks:
- "bunkerweb.NAMESPACE=my-namespace" # Setzen Sie den Namespace für die BunkerWeb-Instanz
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
NAMESPACES: "my-namespace my-other-namespace" # Lauschen Sie nur auf diese Namespaces
...

14
docs/de/plugins.md
View file

@ -89,7 +89,7 @@ Der erste Schritt besteht darin, das Plugin zu installieren, indem Sie seine Dat
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -124,7 +124,7 @@ Der erste Schritt besteht darin, das Plugin zu installieren, indem Sie seine Dat
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -167,7 +167,7 @@ Der erste Schritt besteht darin, das Plugin zu installieren, indem Sie seine Dat
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- /shared/bw-plugins:/data/plugins
...
@ -214,7 +214,7 @@ Der erste Schritt besteht darin, das Plugin zu installieren, indem Sie seine Dat
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE
@ -254,7 +254,7 @@ Der erste Schritt besteht darin, das Plugin zu installieren, indem Sie seine Dat
!!! tip "Bestehende Plugins"
Wenn die Dokumentation nicht ausreicht, können Sie sich den bestehenden Quellcode der [offiziellen Plugins](https://github.com/bunkerity/bunkerweb-plugins) und der [Kern-Plugins](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/common/core) ansehen (bereits in BunkerWeb enthalten, aber technisch gesehen sind es Plugins).
Wenn die Dokumentation nicht ausreicht, können Sie sich den bestehenden Quellcode der [offiziellen Plugins](https://github.com/bunkerity/bunkerweb-plugins) und der [Kern-Plugins](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/common/core) ansehen (bereits in BunkerWeb enthalten, aber technisch gesehen sind es Plugins).
Wie eine Plugin-Struktur aussieht:
```
@ -478,7 +478,7 @@ Die deklarierten Funktionen werden automatisch in bestimmten Kontexten aufgerufe
#### Bibliotheken
Alle Direktiven aus dem [NGINX LUA-Modul](https://github.com/openresty/lua-nginx-module) und dem [NGINX Stream LUA-Modul](https://github.com/openresty/stream-lua-nginx-module) sind verfügbar. Darüber hinaus können Sie die in BunkerWeb enthaltenen LUA-Bibliotheken verwenden: siehe [dieses Skript](https://github.com/bunkerity/bunkerweb/blob/v1.6.9-rc4/src/deps/clone.sh) für die vollständige Liste.
Alle Direktiven aus dem [NGINX LUA-Modul](https://github.com/openresty/lua-nginx-module) und dem [NGINX Stream LUA-Modul](https://github.com/openresty/stream-lua-nginx-module) sind verfügbar. Darüber hinaus können Sie die in BunkerWeb enthaltenen LUA-Bibliotheken verwenden: siehe [dieses Skript](https://github.com/bunkerity/bunkerweb/blob/v1.6.9/src/deps/clone.sh) für die vollständige Liste.
Wenn Sie zusätzliche Bibliotheken benötigen, können Sie diese in den Stammordner des Plugins legen und darauf zugreifen, indem Sie ihnen Ihre Plugin-ID voranstellen. Hier ist ein Beispiel für eine Datei namens **mylibrary.lua**:
@ -559,7 +559,7 @@ end
!!! tip "Weitere Beispiele"
Wenn Sie die vollständige Liste der verfügbaren Funktionen sehen möchten, können Sie sich die Dateien im [lua-Verzeichnis](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/bw/lua/bunkerweb) des Repositorys ansehen.
Wenn Sie die vollständige Liste der verfügbaren Funktionen sehen möchten, können Sie sich die Dateien im [lua-Verzeichnis](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/bw/lua/bunkerweb) des Repositorys ansehen.
### Jobs

34
docs/de/quickstart-guide.md
View file

@ -18,7 +18,7 @@ Diese Schnellstart-Anleitung hilft Ihnen, BunkerWeb schnell zu installieren und
Der Schutz bestehender Webanwendungen, die bereits über das HTTP(S)-Protokoll erreichbar sind, ist das Hauptziel von BunkerWeb: Es fungiert als klassischer [Reverse-Proxy](https://de.wikipedia.org/wiki/Reverse_Proxy) mit zusätzlichen Sicherheitsfunktionen.
Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) des Repositorys finden Sie Beispiele aus der Praxis.
Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) des Repositorys finden Sie Beispiele aus der Praxis.
## Grundlegende Einrichtung
@ -33,7 +33,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Standardmäßig stellt der Container Folgendes bereit:
@ -51,8 +51,8 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
```bash
# Laden Sie das Skript und seine Prüfsumme herunter
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Überprüfen Sie die Prüfsumme
sha256sum -c install-bunkerweb.sh.sha256
@ -90,7 +90,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
services:
bunkerweb:
# Dies ist der Name, der zur Identifizierung der Instanz im Scheduler verwendet wird
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -103,7 +103,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Stellen Sie sicher, dass Sie den richtigen Instanznamen festlegen
@ -120,7 +120,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
restart: "unless-stopped"
@ -187,7 +187,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -203,7 +203,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -221,7 +221,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bw-docker
environment:
@ -244,7 +244,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-docker
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Denken Sie daran, einen stärkeren geheimen Schlüssel festzulegen (siehe Abschnitt Voraussetzungen)
@ -339,7 +339,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -369,7 +369,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- "bunkerweb.INSTANCE=yes"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -387,7 +387,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
<<: *bw-ui-env
DOCKER_HOST: "tcp://bw-docker:2375"
@ -416,7 +416,7 @@ Im [Beispielordner](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examp
- "node.role == manager"
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Denken Sie daran, einen stärkeren geheimen Schlüssel festzulegen (siehe Abschnitt Voraussetzungen)
@ -637,7 +637,7 @@ Sie können sich nun mit dem während des Einrichtungsassistenten erstellten Adm
-e "www.example.com_REVERSE_PROXY_HOST=http://myapp:8080" \
-e "www.example.com_REVERSE_PROXY_URL=/" \
# --- Fügen Sie alle anderen vorhandenen Umgebungsvariablen für UI, Redis, CrowdSec usw. hinzu ---
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ihr Anwendungscontainer (`myapp`) und der `bunkerweb-aio`-Container müssen sich im selben Docker-Netzwerk befinden, damit BunkerWeb ihn über den Hostnamen `myapp` erreichen kann.
@ -659,7 +659,7 @@ Sie können sich nun mit dem während des Einrichtungsassistenten erstellten Adm
-p 443:8443/tcp \
-p 443:8443/udp \
# ... (alle anderen relevanten Umgebungsvariablen wie im Hauptbeispiel oben gezeigt) ...
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Stellen Sie sicher, dass Sie `myapp` durch den tatsächlichen Namen oder die IP Ihres Anwendungscontainers und `http://myapp:8080` durch dessen korrekte Adresse und Port ersetzen.

36
docs/de/upgrading.md
View file

@ -25,16 +25,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -137,20 +137,20 @@
Beispiele:
```bash
# Interaktiv auf 1.6.9~rc4 aktualisieren (fragt nach Sicherung)
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
# Interaktiv auf 1.6.9 aktualisieren (fragt nach Sicherung)
sudo ./install-bunkerweb.sh --version 1.6.9
# Nicht-interaktives Upgrade mit automatischer Sicherung in ein benutzerdefiniertes Verzeichnis
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --backup-dir /var/backups/bw-2025-01 -y
sudo ./install-bunkerweb.sh -v 1.6.9 --backup-dir /var/backups/bw-2025-01 -y
# Stilles unbeaufsichtigtes Upgrade (Protokolle unterdrückt) – verlässt sich auf die standardmäßige automatische Sicherung
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 -y -q
sudo ./install-bunkerweb.sh -v 1.6.9 -y -q
# Einen Probelauf (Plan) durchführen, ohne Änderungen anzuwenden
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --dry-run
sudo ./install-bunkerweb.sh -v 1.6.9 --dry-run
# Upgrade unter Überspringen der automatischen Sicherung (NICHT empfohlen)
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --no-auto-backup -y
sudo ./install-bunkerweb.sh -v 1.6.9 --no-auto-backup -y
```
!!! warning "Überspringen von Sicherungen"
@ -230,7 +230,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Um zu verhindern, dass das BunkerWeb-Paket bei der Ausführung von `apt upgrade` aktualisiert wird, können Sie den folgenden Befehl verwenden:
@ -256,7 +256,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Um zu verhindern, dass das BunkerWeb-Paket bei der Ausführung von `dnf upgrade` aktualisiert wird, können Sie den folgenden Befehl verwenden:
@ -653,16 +653,16 @@ Wir haben eine **Namespace**-Funktion zu den Autoconf-Integrationen hinzugefügt
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -697,7 +697,7 @@ Wir haben eine **Namespace**-Funktion zu den Autoconf-Integrationen hinzugefügt
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Um zu verhindern, dass das BunkerWeb-Paket bei der Ausführung von `apt upgrade` aktualisiert wird, können Sie den folgenden Befehl verwenden:
@ -723,7 +723,7 @@ Wir haben eine **Namespace**-Funktion zu den Autoconf-Integrationen hinzugefügt
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Um zu verhindern, dass das BunkerWeb-Paket bei der Ausführung von `dnf upgrade` aktualisiert wird, können Sie den folgenden Befehl verwenden:

8
docs/de/web-ui.md
View file

@ -35,7 +35,7 @@ Die UI erwartet, dass Scheduler/(BunkerWeb-)API/Redis/DB erreichbar sind.
Verwenden Sie die veröffentlichten Images und das Layout aus dem [Quickstart-Guide](quickstart-guide.md#__tabbed_1_3). Stack starten, dann den Wizard im Browser abschließen.
```bash
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9~rc4-rc1/misc/integrations/docker-compose.yml up -d
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9-rc1/misc/integrations/docker-compose.yml up -d
```
Öffnen Sie den Scheduler-Host (z. B. `https://www.example.com/changeme`) und führen Sie den `/setup`-Wizard aus, um UI, Scheduler und Instanz zu konfigurieren.
@ -52,7 +52,7 @@ Die UI erwartet, dass Scheduler/(BunkerWeb-)API/Redis/DB erreichbar sind.
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -63,7 +63,7 @@ Die UI erwartet, dass Scheduler/(BunkerWeb-)API/Redis/DB erreichbar sind.
networks: [bw-universe, bw-services]
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *service-env
BUNKERWEB_INSTANCES: "bunkerweb"
@ -83,7 +83,7 @@ Die UI erwartet, dass Scheduler/(BunkerWeb-)API/Redis/DB erreichbar sind.
networks: [bw-universe, bw-db]
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *service-env
ADMIN_USERNAME: "admin"

106
docs/es/advanced.md
View file

@ -1,8 +1,8 @@
# Usos avanzados
Muchos ejemplos de casos de uso del mundo real están disponibles en la carpeta [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) del repositorio de GitHub.
Muchos ejemplos de casos de uso del mundo real están disponibles en la carpeta [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) del repositorio de GitHub.
También proporcionamos numerosos boilerplates, como archivos YAML para diversas integraciones y tipos de bases de datos. Estos están disponibles en la carpeta [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations).
También proporcionamos numerosos boilerplates, como archivos YAML para diversas integraciones y tipos de bases de datos. Estos están disponibles en la carpeta [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations).
Esta sección solo se enfoca en usos avanzados y ajustes de seguridad, consulta la [sección de características](features.md) de la documentación para ver todas las configuraciones disponibles.
@ -85,7 +85,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ten en cuenta que si tu contenedor ya está creado, necesitarás eliminarlo y recrearlo para que se actualicen las nuevas variables de entorno.
@ -96,7 +96,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -104,7 +104,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -121,7 +121,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -129,7 +129,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -176,7 +176,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -184,7 +184,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -249,7 +249,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ten en cuenta que si tu contenedor ya está creado, necesitarás eliminarlo y recrearlo para que se actualicen las nuevas variables de entorno.
@ -260,7 +260,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -270,7 +270,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -288,7 +288,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -298,7 +298,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -350,7 +350,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -360,7 +360,7 @@ Encontrarás más configuraciones sobre la IP real en la [sección de caracterí
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -485,8 +485,8 @@ El Manager es el cerebro del clúster. Ejecuta el Scheduler, la base de datos y,
```bash
# Descargar script y checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verificar checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -585,7 +585,7 @@ El Manager es el cerebro del clúster. Ejecuta el Scheduler, la base de datos y,
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: \"192.168.1.11 192.168.1.12\" # Sustituye por las IP de tus workers
@ -604,7 +604,7 @@ El Manager es el cerebro del clúster. Ejecuta el Scheduler, la base de datos y,
- bw-redis
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
ports:
- \"7000:7000\" # Exponer el puerto de la UI
environment:
@ -687,7 +687,7 @@ Los workers son los nodos que procesan el tráfico entrante.
```yaml title="docker-compose.yml"
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- \"80:8080/tcp\"
- \"443:8443/tcp\"
@ -992,7 +992,7 @@ Para habilitar systemd-resolved como tu resolutor de DNS en BunkerWeb, establece
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1020,7 +1020,7 @@ Para habilitar systemd-resolved como tu resolutor de DNS en BunkerWeb, establece
- bw-dns
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1031,7 +1031,7 @@ Para habilitar systemd-resolved como tu resolutor de DNS en BunkerWeb, establece
- bw-dns
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1145,7 +1145,7 @@ Algunas integraciones proporcionan formas más convenientes de aplicar configura
}" \
-p 80:8080/tcp \
-p 443:8443/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ten en cuenta que si tu contenedor ya está creado, necesitarás eliminarlo y recrearlo para que se apliquen las nuevas variables de entorno.
@ -1185,7 +1185,7 @@ Algunas integraciones proporcionan formas más convenientes de aplicar configura
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1208,7 +1208,7 @@ Algunas integraciones proporcionan formas más convenientes de aplicar configura
```yaml
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- |
CUSTOM_CONF_SERVER_HTTP_hello-world=
@ -1251,7 +1251,7 @@ Algunas integraciones proporcionan formas más convenientes de aplicar configura
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1321,7 +1321,7 @@ Algunas integraciones proporcionan formas más convenientes de aplicar configura
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1552,7 +1552,7 @@ Para obtener una lista completa de las configuraciones relacionadas con el modo
-p 443:8443/udp \
-p 10000:10000/tcp \
-p 20000:20000/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ten en cuenta que si tu contenedor ya está creado, necesitarás eliminarlo y recrearlo para que se apliquen las nuevas variables de entorno.
@ -1575,7 +1575,7 @@ Para obtener una lista completa de las configuraciones relacionadas con el modo
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Mantenlo si quieres usar la automatización de Let's Encrypt al usar el tipo de desafío http
- "10000:10000" # app1
@ -1590,7 +1590,7 @@ Para obtener una lista completa de las configuraciones relacionadas con el modo
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Esta configuración es obligatoria para especificar la instancia de BunkerWeb
@ -1641,7 +1641,7 @@ Para obtener una lista completa de las configuraciones relacionadas con el modo
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Mantenlo si quieres usar la automatización de Let's Encrypt cuando usas el tipo de desafío http
- "10000:10000" # app1
@ -1871,7 +1871,7 @@ Para obtener una lista completa de las configuraciones relacionadas con el modo
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
# Mantenlo si quieres usar la automatización de Let's Encrypt cuando usas el tipo de desafío http
- published: 80
@ -2001,7 +2001,7 @@ Se pueden usar las siguientes configuraciones:
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Ten en cuenta que si tu contenedor ya está creado, necesitarás eliminarlo y recrearlo para que se apliquen las nuevas variables de entorno.
@ -2045,7 +2045,7 @@ Se pueden usar las siguientes configuraciones:
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2060,7 +2060,7 @@ Se pueden usar las siguientes configuraciones:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Esta configuración es obligatoria para especificar la instancia de BunkerWeb
@ -2154,7 +2154,7 @@ Se pueden usar las siguientes configuraciones:
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
environment:
@ -2167,7 +2167,7 @@ Se pueden usar las siguientes configuraciones:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "" # No necesitamos especificar la instancia de BunkerWeb aquí, ya que son detectadas automáticamente por el servicio de autoconfiguración
@ -2182,7 +2182,7 @@ Se pueden usar las siguientes configuraciones:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2422,7 +2422,7 @@ Se pueden usar las siguientes configuraciones:
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
volumes:
- /shared/www:/var/www/html
...
@ -2521,7 +2521,7 @@ Por defecto, BunkerWeb solo escuchará en direcciones IPv4 y no usará IPv6 para
```yaml
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
USE_IPv6: "yes"
@ -2661,7 +2661,7 @@ LOG_LEVEL_1=error
services:
bunkerweb:
# Este es el nombre que se usará para identificar la instancia en el Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2674,7 +2674,7 @@ LOG_LEVEL_1=error
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Asegúrate de establecer el nombre correcto de la instancia
@ -2691,7 +2691,7 @@ LOG_LEVEL_1=error
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
volumes:
@ -2826,7 +2826,7 @@ Puede configurar el controlador de registro para sus servicios en su archivo `do
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
logging:
driver: "json-file"
options:
@ -2935,7 +2935,7 @@ Las variables habituales son:
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Si el contenedor ya existe, recréalo para aplicar el nuevo entorno.
@ -2946,7 +2946,7 @@ Las variables habituales son:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -2965,7 +2965,7 @@ Las variables habituales son:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3008,7 +3008,7 @@ Las variables habituales son:
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3960,11 +3960,11 @@ Las plantillas usan sintaxis de plantilla Lua con los siguientes delimitadores:
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
# ... otras configuraciones (no se necesitan variables de entorno aquí para páginas personalizadas)
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./templates:/custom_templates:ro
environment:
@ -4047,7 +4047,7 @@ Las plantillas usan sintaxis de plantilla Lua con los siguientes delimitadores:
spec:
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
env:
- name: CUSTOM_ERROR_PAGE
value: "/custom_templates/error.html"

8
docs/es/api.md
View file

@ -41,7 +41,7 @@ Elige el sabor que encaje con tu entorno.
services:
bunkerweb:
# Nombre que usará el scheduler para identificar la instancia
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -54,7 +54,7 @@ Elige el sabor que encaje con tu entorno.
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Asegúrate de poner el nombre de instancia correcto
@ -76,7 +76,7 @@ Elige el sabor que encaje con tu entorno.
- bw-db
bw-api:
image: bunkerity/bunkerweb-api:1.6.9-rc4
image: bunkerity/bunkerweb-api:1.6.9
environment:
<<: *bw-env
API_USERNAME: "admin"
@ -143,7 +143,7 @@ Elige el sabor que encaje con tu entorno.
-e SERVICE_API=yes \
-e API_WHITELIST_IPS="127.0.0.0/8" \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Linux"

4
docs/es/concepts.md
View file

@ -105,7 +105,7 @@ Ten en cuenta que el modo multisitio es implícito cuando se utiliza la interfaz
!!! info "Para saber más"
Encontrarás ejemplos concretos del modo multisitio en los [usos avanzados](advanced.md) de la documentación y en el directorio de [ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) del repositorio.
Encontrarás ejemplos concretos del modo multisitio en los [usos avanzados](advanced.md) de la documentación y en el directorio de [ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) del repositorio.
## Configuraciones personalizadas {#custom-configurations}
@ -126,7 +126,7 @@ La gestión de configuraciones personalizadas desde la interfaz de usuario web s
!!! info "Para saber más"
Encontrarás ejemplos concretos de configuraciones personalizadas en los [usos avanzados](advanced.md#custom-configurations) de la documentación y en el directorio de [ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) del repositorio.
Encontrarás ejemplos concretos de configuraciones personalizadas en los [usos avanzados](advanced.md#custom-configurations) de la documentación y en el directorio de [ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) del repositorio.
## Base de datos

4
docs/es/features.md
View file

@ -1734,7 +1734,7 @@ Las siguientes secciones desarrollan cada paso.
services:
bunkerweb:
# Este es el nombre que se utilizará para identificar la instancia en el Planificador
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1751,7 +1751,7 @@ Las siguientes secciones desarrollan cada paso.
syslog-address: "udp://10.20.30.254:514" # La dirección IP del servicio syslog
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Asegúrese de establecer el nombre de instancia correcto

108
docs/es/integrations.md
View file

@ -1268,7 +1268,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Por defecto, el contenedor expone:
@ -1284,7 +1284,7 @@ Se requiere un volumen nombrado (o un bind mount) para persistir la base de dato
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
volumes:
- bw-storage:/data
...
@ -1361,7 +1361,7 @@ docker run -d \
-e API_PASSWORD=StrongP@ssw0rd \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
-p 8888:8888/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Recomendado (detrás de BunkerWeb) — no publiques el `8888`; en su lugar, haz un proxy inverso:
@ -1369,7 +1369,7 @@ Recomendado (detrás de BunkerWeb) — no publiques el `8888`; en su lugar, haz
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1441,7 +1441,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* Cuando `USE_CROWDSEC=yes`, el punto de entrada hará lo siguiente:
@ -1496,7 +1496,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
!!! info "Cómo funciona internamente"
@ -1518,7 +1518,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Notas:
@ -1554,7 +1554,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* El **registro local** se omite cuando `CROWDSEC_API` no es `127.0.0.1` o `localhost`.
@ -1586,13 +1586,13 @@ Al acceder a estas imágenes preconstruidas desde Docker Hub, puedes obtener y e
Ya sea que estés realizando pruebas, desarrollando aplicaciones o desplegando BunkerWeb en producción, la opción de contenedorización de Docker proporciona flexibilidad y facilidad de uso. Adoptar este método te permite aprovechar al máximo las características de BunkerWeb mientras te beneficias de las ventajas de la tecnología Docker.
```shell
docker pull bunkerity/bunkerweb:1.6.9-rc4
docker pull bunkerity/bunkerweb:1.6.9
```
Las imágenes de Docker también están disponibles en [GitHub packages](https://github.com/orgs/bunkerity/packages?repo_name=bunkerweb) y se pueden descargar usando la dirección del repositorio `ghcr.io`:
```shell
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9-rc4
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9
```
Los conceptos clave para la integración con Docker incluyen:
@ -1602,7 +1602,7 @@ Los conceptos clave para la integración con Docker incluyen:
- **Redes**: Las redes de Docker desempeñan un papel vital en la integración de BunkerWeb. Estas redes tienen dos propósitos principales: exponer puertos a los clientes y conectarse a los servicios web ascendentes. Al exponer los puertos, BunkerWeb puede aceptar solicitudes entrantes de los clientes, permitiéndoles acceder a los servicios web protegidos. Además, al conectarse a los servicios web ascendentes, BunkerWeb puede enrutar y gestionar el tráfico de manera eficiente, proporcionando una mayor seguridad y rendimiento.
!!! info "Backend de la base de datos"
Ten en cuenta que nuestras instrucciones asumen que estás utilizando SQLite como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, también se admiten otros backends de bases de datos. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) del repositorio para obtener más información.
Ten en cuenta que nuestras instrucciones asumen que estás utilizando SQLite como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, también se admiten otros backends de bases de datos. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) del repositorio para obtener más información.
### Variables de entorno
@ -1612,7 +1612,7 @@ Las configuraciones se pasan al Programador usando las variables de entorno de D
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- MY_SETTING=value
- ANOTHER_SETTING=another value
@ -1656,7 +1656,7 @@ Esto asegura que las configuraciones sensibles se mantengan fuera del entorno y
El [programador](concepts.md#scheduler) se ejecuta en su propio contenedor, que también está disponible en Docker Hub:
```shell
docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
docker pull bunkerity/bunkerweb-scheduler:1.6.9
```
!!! info "Configuraciones de BunkerWeb"
@ -1677,7 +1677,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
environment:
# Esto establecerá las configuraciones de la API para el contenedor de BunkerWeb
<<: *bw-api-env
@ -1686,7 +1686,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
- bw-universe
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
# Esto establecerá las configuraciones de la API para el contenedor del Programador
<<: *bw-api-env
@ -1704,7 +1704,7 @@ Se necesita un volumen para almacenar la base de datos SQLite y las copias de se
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- bw-storage:/data
...
@ -1850,7 +1850,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1863,7 +1863,7 @@ services:
- bw-universe
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # Esta configuración es obligatoria para especificar la instancia de BunkerWeb
@ -1896,7 +1896,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1909,7 +1909,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
environment:
@ -1975,8 +1975,8 @@ Para empezar, descarga el script de instalación y su suma de verificación, lue
```bash
# Descargar el script y su suma de verificación
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verificar la suma de verificación
sha256sum -c install-bunkerweb.sh.sha256
@ -2035,7 +2035,7 @@ Para configuraciones no interactivas o automatizadas, el script se puede control
| Opción | Descripción |
| :---------------------- | :------------------------------------------------------------------------------------------------ |
| `-v, --version VERSION` | Especifica la versión de BunkerWeb a instalar (p. ej., `1.6.9~rc4`). |
| `-v, --version VERSION` | Especifica la versión de BunkerWeb a instalar (p. ej., `1.6.9`). |
| `-w, --enable-wizard` | Habilita el asistente de configuración. |
| `-n, --no-wizard` | Deshabilita el asistente de configuración. |
| `-y, --yes` | Se ejecuta en modo no interactivo usando las respuestas predeterminadas para todas las preguntas. |
@ -2100,7 +2100,7 @@ sudo ./install-bunkerweb.sh --yes
sudo ./install-bunkerweb.sh --worker --no-wizard
# Instalar una versión específica
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
sudo ./install-bunkerweb.sh --version 1.6.9
# Configuración del Gestor con instancias de trabajador remotas (se requieren instancias)
sudo ./install-bunkerweb.sh --manager --instances "192.168.1.10 192.168.1.11"
@ -2244,12 +2244,12 @@ Asegúrate de tener **NGINX 1.28.2 instalado antes de instalar BunkerWeb**. Para
export UI_WIZARD=no
```
Y finalmente instala BunkerWeb 1.6.9~rc4:
Y finalmente instala BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Para evitar la actualización de los paquetes de NGINX y/o BunkerWeb al ejecutar `apt upgrade`, puedes usar el siguiente comando:
@ -2292,12 +2292,12 @@ Asegúrate de tener **NGINX 1.28.2 instalado antes de instalar BunkerWeb**. Para
export UI_WIZARD=no
```
Y finalmente instala BunkerWeb 1.6.9~rc4:
Y finalmente instala BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Para evitar la actualización de los paquetes de NGINX y/o BunkerWeb al ejecutar `apt upgrade`, puedes usar el siguiente comando:
@ -2328,12 +2328,12 @@ Asegúrate de tener **NGINX 1.28.2 instalado antes de instalar BunkerWeb**. Para
export UI_WIZARD=no
```
Y finalmente instala BunkerWeb 1.6.9~rc4:
Y finalmente instala BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf makecache && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Para evitar la actualización de los paquetes de NGINX y/o BunkerWeb al ejecutar `dnf upgrade`, puedes usar el siguiente comando:
@ -2378,12 +2378,12 @@ Asegúrate de tener **NGINX 1.28.2 instalado antes de instalar BunkerWeb**. Para
export UI_WIZARD=no
```
Y finalmente instala BunkerWeb 1.6.9~rc4:
Y finalmente instala BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Para evitar la actualización de los paquetes de NGINX y/o BunkerWeb al ejecutar `dnf upgrade`, puedes usar el siguiente comando:
@ -2476,7 +2476,7 @@ Al adoptar este enfoque, puedes disfrutar de la reconfiguración en tiempo real
La integración de autoconfiguración de Docker implica el uso del **modo multisitio**. Por favor, consulta la [sección de multisitio](concepts.md#multisite-mode) de la documentación para obtener más información.
!!! info "Backend de la base de datos"
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) del repositorio para obtener más información.
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) del repositorio para obtener más información.
Para habilitar las actualizaciones de configuración automatizadas, incluye un contenedor adicional llamado `bw-autoconf` en la pila. Este contenedor aloja el servicio de autoconfiguración, que gestiona los cambios de configuración dinámicos para BunkerWeb.
@ -2490,7 +2490,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2505,7 +2505,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # No necesitamos especificar la instancia de BunkerWeb aquí, ya que son detectadas automáticamente por el servicio de autoconfiguración
@ -2520,7 +2520,7 @@ services:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2703,13 +2703,13 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
- "bunkerweb.NAMESPACE=my-namespace" # Establece el espacio de nombres para la instancia de BunkerWeb para que el servicio de autoconfiguración pueda detectarla
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
...
NAMESPACES: "my-namespace my-other-namespace" # Solo escucha a estos espacios de nombres
@ -2761,7 +2761,7 @@ Para una configuración óptima, se recomienda definir BunkerWeb como un **[Daem
Dada la presencia de múltiples instancias de BunkerWeb, es necesario establecer un almacén de datos compartido implementado como un servicio de [Redis](https://redis.io/) o [Valkey](https://valkey.io/). Este servicio será utilizado por las instancias para almacenar en caché y compartir datos entre ellas. Se puede encontrar más información sobre la configuración de Redis/Valkey [aquí](features.md#redis).
!!! info "Backend de la base de datos"
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) del repositorio para obtener más información.
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) del repositorio para obtener más información.
La configuración de backends de bases de datos en clúster está fuera del alcance de esta documentación.
@ -2876,7 +2876,7 @@ The **BunkerWeb controller** automatically discovers pods with BunkerWeb sidecar
```yaml
controller:
enabled: true
tag: "1.6.9~rc4"
tag: "1.6.9"
```
2. For each sidecar, add:
@ -2969,7 +2969,7 @@ In your BunkerWeb chart `values.yaml`, configure the `BUNKERWEB_INSTANCES` envir
```yaml
scheduler:
tag: "1.6.9~rc4"
tag: "1.6.9"
extraEnvs:
- name: BUNKERWEB_INSTANCES
value: "http://app1-bunkerweb-workers.namespace.svc.cluster.local:5000 http://app2-bunkerweb-workers.namespace.svc.cluster.local:5000"
@ -3013,7 +3013,7 @@ spec:
# BunkerWeb Sidecar
- name: bunkerweb
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- containerPort: 8080 # Exposed HTTP port
- containerPort: 5000 # Internal API (mandatory)
@ -3284,7 +3284,7 @@ To add a new application protected by BunkerWeb:
#### Archivos YAML completos
En lugar de usar el chart de Helm, también puedes usar las plantillas YAML dentro de la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) del repositorio de GitHub. Ten en cuenta que recomendamos encarecidamente usar el chart de Helm en su lugar.
En lugar de usar el chart de Helm, también puedes usar las plantillas YAML dentro de la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) del repositorio de GitHub. Ten en cuenta que recomendamos encarecidamente usar el chart de Helm en su lugar.
### Recursos de Ingress
@ -3432,7 +3432,7 @@ metadata:
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
imagePullPolicy: Always
env:
- name: NAMESPACES
@ -3605,11 +3605,11 @@ service:
# Configuraciones de BunkerWeb
bunkerweb:
tag: 1.6.9~rc4
tag: 1.6.9
# Configuraciones del programador
scheduler:
tag: 1.6.9~rc4
tag: 1.6.9
extraEnvs:
# Habilita el módulo de IP real para obtener la IP real de los clientes
- name: USE_REAL_IP
@ -3617,11 +3617,11 @@ scheduler:
# Configuraciones del controlador
controller:
tag: 1.6.9~rc4
tag: 1.6.9
# Configuraciones de la UI
ui:
tag: 1.6.9~rc4
tag: 1.6.9
```
Instala BunkerWeb con valores personalizados:
@ -4243,7 +4243,7 @@ Dado que se están ejecutando múltiples instancias de BunkerWeb, se debe crear
En cuanto al volumen de la base de datos, la documentación no especifica un enfoque concreto. La elección de una carpeta compartida o un controlador específico para el volumen de la base de datos depende de tu caso de uso particular y se deja como ejercicio para el lector.
!!! info "Backend de la base de datos"
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) del repositorio para obtener más información.
Ten en cuenta que nuestras instrucciones asumen que estás utilizando MariaDB como el backend de base de datos predeterminado, según lo configurado por el ajuste `DATABASE_URI`. Sin embargo, entendemos que puedes preferir utilizar backends alternativos para tu integración con Docker. Si ese es el caso, ten la seguridad de que otros backends de bases de datos también son posibles. Consulta los archivos docker-compose en la [carpeta misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) del repositorio para obtener más información.
La configuración de backends de bases de datos en clúster está fuera del alcance de esta documentación.
@ -4257,7 +4257,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -4286,7 +4286,7 @@ services:
- "bunkerweb.INSTANCE=yes" # Etiqueta obligatoria para que el servicio de autoconfiguración identifique la instancia de BunkerWeb
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # No necesitamos especificar la instancia de BunkerWeb aquí, ya que son detectadas automáticamente por el servicio de autoconfiguración
@ -4307,7 +4307,7 @@ services:
- "node.role == worker"
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
SWARM_MODE: "yes"
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Recuerda establecer una contraseña más segura para la base de datos
@ -4459,7 +4459,7 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
deploy:
mode: global
@ -4471,7 +4471,7 @@ networks:
- "bunkerweb.NAMESPACE=my-namespace" # Establece el espacio de nombres para la instancia de BunkerWeb
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
NAMESPACES: "my-namespace my-other-namespace" # Solo escucha a estos espacios de nombres
...

12
docs/es/plugins.md
View file

@ -89,7 +89,7 @@ El primer paso es instalar el plugin colocando sus archivos dentro de la carpeta
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -125,7 +125,7 @@ El primer paso es instalar el plugin colocando sus archivos dentro de la carpeta
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -168,7 +168,7 @@ El primer paso es instalar el plugin colocando sus archivos dentro de la carpeta
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- /shared/bw-plugins:/data/plugins
...
@ -215,7 +215,7 @@ El primer paso es instalar el plugin colocando sus archivos dentro de la carpeta
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE
@ -255,7 +255,7 @@ El primer paso es instalar el plugin colocando sus archivos dentro de la carpeta
!!! tip "Plugins existentes"
Si la documentación no es suficiente, puedes echar un vistazo al código fuente existente de los [plugins oficiales](https://github.com/bunkerity/bunkerweb-plugins) y los [plugins del núcleo](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/common/core) (ya incluidos en BunkerWeb, pero técnicamente son plugins).
Si la documentación no es suficiente, puedes echar un vistazo al código fuente existente de los [plugins oficiales](https://github.com/bunkerity/bunkerweb-plugins) y los [plugins del núcleo](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/common/core) (ya incluidos en BunkerWeb, pero técnicamente son plugins).
Así es como se ve la estructura de un plugin:
```
@ -560,7 +560,7 @@ end
!!! tip "Más ejemplos"
Si quieres ver la lista completa de funciones disponibles, puedes echar un vistazo a los archivos presentes en el [directorio lua](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/bw/lua/bunkerweb) del repositorio.
Si quieres ver la lista completa de funciones disponibles, puedes echar un vistazo a los archivos presentes en el [directorio lua](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/bw/lua/bunkerweb) del repositorio.
### Trabajos

34
docs/es/quickstart-guide.md
View file

@ -18,7 +18,7 @@ Esta guía de inicio rápido te ayudará a instalar rápidamente BunkerWeb y a p
Proteger las aplicaciones web existentes que ya son accesibles con el protocolo HTTP(S) es el objetivo principal de BunkerWeb: actuará como un [proxy inverso](https://es.wikipedia.org/wiki/Proxy_inverso) clásico con características de seguridad adicionales.
Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) del repositorio para obtener ejemplos del mundo real.
Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) del repositorio para obtener ejemplos del mundo real.
## Configuración básica
@ -33,7 +33,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Por defecto, el contenedor expone:
@ -52,8 +52,8 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
```bash
```bash
# Download the script and its checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify the checksum
sha256sum -c install-bunkerweb.sh.sha256 # Si la comprobación es exitosa, ejecuta el script
@ -89,7 +89,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
services:
bunkerweb:
# Este es el nombre que se usará para identificar la instancia en el Programador
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -102,7 +102,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Asegúrate de establecer el nombre de instancia correcto
@ -119,7 +119,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
restart: "unless-stopped"
@ -186,7 +186,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -202,7 +202,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -220,7 +220,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bw-docker
environment:
@ -243,7 +243,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-docker
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Recuerda establecer una clave secreta más segura (consulta la sección de Requisitos previos)
@ -338,7 +338,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -368,7 +368,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- "bunkerweb.INSTANCE=yes"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -386,7 +386,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
<<: *bw-ui-env
DOCKER_HOST: "tcp://bw-docker:2375"
@ -415,7 +415,7 @@ Consulta la [carpeta de ejemplos](https://github.com/bunkerity/bunkerweb/tree/v1
- "node.role == manager"
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Recuerda establecer una clave secreta más segura (consulta la sección de Requisitos previos)
@ -637,7 +637,7 @@ Ahora puedes iniciar sesión con la cuenta de administrador que creaste durante
-e "www.example.com_REVERSE_PROXY_HOST=http://myapp:8080" \
-e "www.example.com_REVERSE_PROXY_URL=/" \
# --- Incluye cualquier otra variable de entorno existente para la UI, Redis, CrowdSec, etc. ---
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Tu contenedor de aplicación (`myapp`) y el contenedor `bunkerweb-aio` deben estar en la misma red de Docker para que BunkerWeb pueda alcanzarlo usando el nombre de host `myapp`.
@ -659,7 +659,7 @@ Ahora puedes iniciar sesión con la cuenta de administrador que creaste durante
-p 443:8443/tcp \
-p 443:8443/udp \
# ... (todas las demás variables de entorno relevantes como se muestra en el ejemplo principal anterior) ...
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Asegúrate de reemplazar `myapp` con el nombre o IP real de tu contenedor de aplicación y `http://myapp:8080` con su dirección y puerto correctos.

36
docs/es/upgrading.md
View file

@ -25,16 +25,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -141,20 +141,20 @@
Ejemplos:
```bash
# Actualizar a 1.6.9~rc4 interactivamente (pedirá confirmación para la copia de seguridad)
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
# Actualizar a 1.6.9 interactivamente (pedirá confirmación para la copia de seguridad)
sudo ./install-bunkerweb.sh --version 1.6.9
# Actualización no interactiva con copia de seguridad automática a un directorio personalizado
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --backup-dir /var/backups/bw-2025-01 -y
sudo ./install-bunkerweb.sh -v 1.6.9 --backup-dir /var/backups/bw-2025-01 -y
# Actualización desatendida silenciosa (salida suprimida) – depende de la copia de seguridad automática predeterminada
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 -y -q
sudo ./install-bunkerweb.sh -v 1.6.9 -y -q
# Realizar una ejecución de prueba (plan) sin aplicar cambios
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --dry-run
sudo ./install-bunkerweb.sh -v 1.6.9 --dry-run
# Actualizar omitiendo la copia de seguridad automática (NO recomendado)
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --no-auto-backup -y
sudo ./install-bunkerweb.sh -v 1.6.9 --no-auto-backup -y
```
!!! warning "Omitir copias de seguridad"
@ -234,7 +234,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Para evitar que el paquete de BunkerWeb se actualice al ejecutar `apt upgrade`, puedes usar el siguiente comando:
@ -260,7 +260,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Para evitar que el paquete de BunkerWeb se actualice al ejecutar `dnf upgrade`, puedes usar el siguiente comando:
@ -657,16 +657,16 @@ Hemos añadido una característica de **espacio de nombres** a las integraciones
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -701,7 +701,7 @@ Hemos añadido una característica de **espacio de nombres** a las integraciones
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Para evitar que el paquete de BunkerWeb se actualice al ejecutar `apt upgrade`, puedes usar el siguiente comando:
@ -727,7 +727,7 @@ Hemos añadido una característica de **espacio de nombres** a las integraciones
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Para evitar que el paquete de BunkerWeb se actualice al ejecutar `dnf upgrade`, puedes usar el siguiente comando:

8
docs/es/web-ui.md
View file

@ -35,7 +35,7 @@ La UI requiere scheduler/API de BunkerWeb/redis/base de datos accesibles.
Usa las imágenes publicadas y el layout del [guía rápida](quickstart-guide.md#__tabbed_1_3) para levantar el stack, luego completa el asistente en el navegador.
```bash
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9~rc4-rc1/misc/integrations/docker-compose.yml up -d
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9-rc1/misc/integrations/docker-compose.yml up -d
```
Visita el hostname del scheduler (ej. `https://www.example.com/changeme`) y ejecuta el asistente `/setup` para configurar la UI, el scheduler y la instancia.
@ -52,7 +52,7 @@ La UI requiere scheduler/API de BunkerWeb/redis/base de datos accesibles.
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -63,7 +63,7 @@ La UI requiere scheduler/API de BunkerWeb/redis/base de datos accesibles.
networks: [bw-universe, bw-services]
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *service-env
BUNKERWEB_INSTANCES: "bunkerweb"
@ -83,7 +83,7 @@ La UI requiere scheduler/API de BunkerWeb/redis/base de datos accesibles.
networks: [bw-universe, bw-db]
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *service-env
ADMIN_USERNAME: "admin"

4
docs/features.md
View file

@ -1770,7 +1770,7 @@ Follow one of the environment-specific guides below so the CrowdSec agent ingest
services:
bunkerweb:
# This is the name that will be used to identify the instance in the Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1787,7 +1787,7 @@ Follow one of the environment-specific guides below so the CrowdSec agent ingest
syslog-address: "udp://10.20.30.254:514" # The IP address of the syslog service
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name

106
docs/fr/advanced.md
View file

@ -1,8 +1,8 @@
# Utilisations avancées
De nombreux exemples de cas d'utilisation concrets sont disponibles dans le dossier [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) du dépôt GitHub.
De nombreux exemples de cas d'utilisation concrets sont disponibles dans le dossier [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) du dépôt GitHub.
Nous fournissons également de nombreux modèles standard, tels que des fichiers YAML pour diverses intégrations et types de bases de données. Ceux-ci sont disponibles dans le dossier [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations).
Nous fournissons également de nombreux modèles standard, tels que des fichiers YAML pour diverses intégrations et types de bases de données. Ceux-ci sont disponibles dans le dossier [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations).
Cette section se concentre uniquement sur les utilisations avancées et le réglage de la sécurité, consultez la [section fonctionnalités](features.md) de la documentation pour voir tous les paramètres disponibles.
@ -85,7 +85,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Veuillez noter que si votre conteneur existe déjà, vous devrez le supprimer et le recréer afin que les nouvelles variables d'environnement soient prises en compte.
@ -96,7 +96,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -104,7 +104,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -121,7 +121,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -129,7 +129,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -176,7 +176,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -184,7 +184,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -249,7 +249,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Veuillez noter que si votre conteneur existe déjà, vous devrez le supprimer et le recréer afin que les nouvelles variables d'environnement soient prises en compte.
@ -260,7 +260,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -270,7 +270,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -288,7 +288,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -298,7 +298,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -350,7 +350,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -360,7 +360,7 @@ Vous trouverez plus de paramètres sur l'IP réelle dans la [section des fonctio
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -485,8 +485,8 @@ Le Manager est le cerveau du cluster. Il exécute le Scheduler, la base de donn
```bash
# Télécharger le script et sa somme
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Vérifier l'empreinte
sha256sum -c install-bunkerweb.sh.sha256
@ -585,7 +585,7 @@ Le Manager est le cerveau du cluster. Il exécute le Scheduler, la base de donn
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: "192.168.1.11 192.168.1.12" # Remplacez par les IPs de vos workers
@ -604,7 +604,7 @@ Le Manager est le cerveau du cluster. Il exécute le Scheduler, la base de donn
- bw-redis
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
ports:
- "7000:7000" # Exposer le port de l'UI
environment:
@ -687,7 +687,7 @@ Les workers sont les nœuds qui traitent le trafic entrant.
```yaml title="docker-compose.yml"
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -992,7 +992,7 @@ Pour activer systemd-resolved comme résolveur DNS dans BunkerWeb, définissez l
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1020,7 +1020,7 @@ Pour activer systemd-resolved comme résolveur DNS dans BunkerWeb, définissez l
- bw-dns
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1031,7 +1031,7 @@ Pour activer systemd-resolved comme résolveur DNS dans BunkerWeb, définissez l
- bw-dns
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1145,7 +1145,7 @@ Certaines intégrations offrent des moyens plus pratiques d'appliquer des config
}" \
-p 80:8080/tcp \
-p 443:8443/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Veuillez noter que si votre conteneur est déjà créé, vous devrez le supprimer et le recréer pour que les nouvelles variables d'environnement soient appliquées.
@ -1185,7 +1185,7 @@ Certaines intégrations offrent des moyens plus pratiques d'appliquer des config
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1208,7 +1208,7 @@ Certaines intégrations offrent des moyens plus pratiques d'appliquer des config
```yaml
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- |
CUSTOM_CONF_SERVER_HTTP_hello-world=
@ -1251,7 +1251,7 @@ Certaines intégrations offrent des moyens plus pratiques d'appliquer des config
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1321,7 +1321,7 @@ Certaines intégrations offrent des moyens plus pratiques d'appliquer des config
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1551,7 +1551,7 @@ Pour la liste complète des paramètres concernant `stream` le mode, veuillez v
-p 443:8443/udp \
-p 10000:10000/tcp \
-p 20000:20000/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Veuillez noter que si votre conteneur existe déjà, vous devrez le supprimer et le recréer afin que les nouvelles variables d'environnement soient prises en compte.
@ -1574,7 +1574,7 @@ Pour la liste complète des paramètres concernant `stream` le mode, veuillez v
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
- "10000:10000" # app1
@ -1589,7 +1589,7 @@ Pour la liste complète des paramètres concernant `stream` le mode, veuillez v
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -1640,7 +1640,7 @@ Pour la liste complète des paramètres concernant `stream` le mode, veuillez v
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
- "10000:10000" # app1
@ -1870,7 +1870,7 @@ Pour la liste complète des paramètres concernant `stream` le mode, veuillez v
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
# Keep it if you want to use Let's Encrypt automation when using http challenge type
- published: 80
@ -2000,7 +2000,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Veuillez noter que si votre conteneur est déjà créé, vous devrez le supprimer et le recréer pour que les nouvelles variables d'environnement soient appliquées.
@ -2044,7 +2044,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2059,7 +2059,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -2153,7 +2153,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
environment:
@ -2166,7 +2166,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -2181,7 +2181,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2421,7 +2421,7 @@ BunkerWeb prend en charge PHP en utilisant des instances [PHP-FPM externes ou ]
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
volumes:
- /shared/www:/var/www/html
...
@ -2520,7 +2520,7 @@ Par défaut, BunkerWeb n'écoutera que les adresses IPv4 et n'utilisera pas IPv6
```yaml
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
USE_IPv6: "yes"
@ -2660,7 +2660,7 @@ LOG_LEVEL_1=error
services:
bunkerweb:
# Ceci est le nom qui sera utilisé pour identifier l'instance dans le Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2673,7 +2673,7 @@ LOG_LEVEL_1=error
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Assurez-vous de définir le nom d'instance correct
@ -2690,7 +2690,7 @@ LOG_LEVEL_1=error
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
volumes:
@ -2825,7 +2825,7 @@ Vous pouvez configurer le pilote de journalisation pour vos services dans votre
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
logging:
driver: "json-file"
options:
@ -2934,7 +2934,7 @@ Les variables couramment utilisées sont :
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Si le conteneur existe déjà, recréez-le pour appliquer le nouvel environnement.
@ -2945,7 +2945,7 @@ Les variables couramment utilisées sont :
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -2964,7 +2964,7 @@ Les variables couramment utilisées sont :
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3007,7 +3007,7 @@ Les variables couramment utilisées sont :
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3959,11 +3959,11 @@ Les modèles utilisent la syntaxe de modèle Lua avec les délimiteurs suivants
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
# ... autres paramètres (pas de variables d'environnement nécessaires ici pour les pages personnalisées)
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./templates:/custom_templates:ro
environment:
@ -4046,7 +4046,7 @@ Les modèles utilisent la syntaxe de modèle Lua avec les délimiteurs suivants
spec:
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
env:
- name: CUSTOM_ERROR_PAGE
value: "/custom_templates/error.html"

8
docs/fr/api.md
View file

@ -41,7 +41,7 @@ Choisissez la saveur adaptée à votre environnement.
services:
bunkerweb:
# Nom utilisé par le scheduler pour identifier l’instance
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -54,7 +54,7 @@ Choisissez la saveur adaptée à votre environnement.
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Assurez-vous de mettre le bon nom d’instance
@ -76,7 +76,7 @@ Choisissez la saveur adaptée à votre environnement.
- bw-db
bw-api:
image: bunkerity/bunkerweb-api:1.6.9-rc4
image: bunkerity/bunkerweb-api:1.6.9
environment:
<<: *bw-env
API_USERNAME: "admin"
@ -143,7 +143,7 @@ Choisissez la saveur adaptée à votre environnement.
-e SERVICE_API=yes \
-e API_WHITELIST_IPS="127.0.0.0/8" \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Linux"

4
docs/fr/concepts.md
View file

@ -105,7 +105,7 @@ Veuillez noter que le mode multisite est implicite lors de l'utilisation de l'in
!!! info "Aller plus loin"
Vous trouverez des exemples concrets du mode multisite dans la section [Utilisations avancées](advanced.md) de la documentation et dans le répertoire [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) du dépôt.
Vous trouverez des exemples concrets du mode multisite dans la section [Utilisations avancées](advanced.md) de la documentation et dans le répertoire [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) du dépôt.
## Configurations personnalisées {#custom-configurations}
@ -126,7 +126,7 @@ La gestion des configurations personnalisées à partir de l'interface utilisate
!!! info "Aller plus loin"
Vous trouverez des exemples concrets de configurations personnalisées dans la section [Utilisations avancées](advanced.md#custom-configurations) de la documentation et dans le répertoire [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) du dépôt.
Vous trouverez des exemples concrets de configurations personnalisées dans la section [Utilisations avancées](advanced.md#custom-configurations) de la documentation et dans le répertoire [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) du dépôt.
## Base de données

4
docs/fr/features.md
View file

@ -1543,7 +1543,7 @@ Les sections suivantes détaillent chacune de ces étapes.
services:
bunkerweb:
# C'est le nom qui sera utilisé pour identifier l'instance dans le planificateur
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1560,7 +1560,7 @@ Les sections suivantes détaillent chacune de ces étapes.
syslog-address: "udp://10.20.30.254:514" # L'adresse IP du service syslog
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Assurez-vous de définir le nom correct de l'instance

108
docs/fr/integrations.md
View file

@ -1268,7 +1268,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Par défaut, le conteneur expose :
@ -1283,7 +1283,7 @@ Un volume nommé (ou un bind mount) est nécessaire pour conserver la base SQLit
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
volumes:
- bw-storage:/data
@ -1361,7 +1361,7 @@ docker run -d \
-e API_PASSWORD=StrongP@ssw0rd \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
-p 8888:8888/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Configuration recommandée (derrière BunkerWeb) — ne publiez pas `8888` ; utilisez plutôt un proxy inverse :
@ -1369,7 +1369,7 @@ Configuration recommandée (derrière BunkerWeb) — ne publiez pas `8888` ; u
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1441,7 +1441,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* Lorsque `USE_CROWDSEC=yes`, le point d'entrée :
@ -1496,7 +1496,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
!!! info "Comment ça marche en interne"
@ -1517,7 +1517,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Notes :
@ -1553,7 +1553,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* **L'enregistrement local** est ignoré lorsque n' `CROWDSEC_API` est pas `127.0.0.1` ou `localhost`.
@ -1587,13 +1587,13 @@ En accédant à ces images prédéfinies à partir de Docker Hub, vous pouvez ra
Que vous effectuiez des tests, développiez des applications ou déployiez BunkerWeb en production, l'option de conteneurisation Docker offre flexibilité et facilité d'utilisation. L'adoption de cette méthode vous permet de tirer pleinement parti des fonctionnalités de BunkerWeb tout en tirant parti des avantages de la technologie Docker.
```shell
docker pull bunkerity/bunkerweb:1.6.9-rc4
docker pull bunkerity/bunkerweb:1.6.9
```
Les images Docker sont également disponibles sur [les packages GitHub](https://github.com/orgs/bunkerity/packages?repo_name=bunkerweb) et peuvent être téléchargées à l'aide de l'adresse du `ghcr.io` dépôt :
```shell
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9-rc4
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9
```
Les concepts clés de l'intégration Docker sont les suivants :
@ -1603,7 +1603,7 @@ Les concepts clés de l'intégration Docker sont les suivants :
- **Réseaux**: Les réseaux Docker jouent un rôle essentiel dans l'intégration de BunkerWeb. Ces réseaux ont deux objectifs principaux : exposer les ports aux clients et se connecter aux services Web en amont. En exposant les ports, BunkerWeb peut accepter les demandes entrantes des clients, leur permettant d'accéder aux services Web protégés. De plus, en se connectant aux services Web en amont, BunkerWeb peut acheminer et gérer efficacement le trafic, offrant ainsi une sécurité et des performances améliorées.
!!! info "Backend de base de données"
Veuillez noter que nos instructions supposent que vous utilisez SQLite comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, d'autres backends de base de données sont également pris en charge. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) du dépôt.
Veuillez noter que nos instructions supposent que vous utilisez SQLite comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, d'autres backends de base de données sont également pris en charge. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) du dépôt.
### Variables d'environnement
@ -1613,7 +1613,7 @@ Les paramètres sont transmis au Scheduler à l'aide de variables d'environnemen
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- MY_SETTING=value
- ANOTHER_SETTING=another value
@ -1657,7 +1657,7 @@ Cela garantit que les paramètres sensibles sont tenus à l'écart de l'environn
Le [Scheduler](concepts.md#scheduler) s'exécute dans son propre conteneur, qui est également disponible sur Docker Hub :
```shell
docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
docker pull bunkerity/bunkerweb-scheduler:1.6.9
```
!!! info "Paramètres BunkerWeb"
@ -1678,7 +1678,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
environment:
# Paramètres API pour le conteneur BunkerWeb
<<: *bw-api-env
@ -1687,7 +1687,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
- bw-universe
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
# Paramètres API pour le conteneur Scheduler
<<: *bw-api-env
@ -1705,7 +1705,7 @@ Un volume est nécessaire pour stocker la base de données SQLite et les sauvega
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- bw-storage:/data
...
@ -1851,7 +1851,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1864,7 +1864,7 @@ services:
- bw-universe
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -1897,7 +1897,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1910,7 +1910,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
environment:
@ -1976,8 +1976,8 @@ Pour commencer, téléchargez le script d'installation et sa somme de contrôle,
```bash
# Download the script and its checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify the checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -2033,7 +2033,7 @@ Pour les configurations non interactives ou automatisées, le script peut être
| Option | Description |
| ----------------------- | -------------------------------------------------------------------------------------------------------- |
| `-v, --version VERSION` | Spécifie la version de BunkerWeb à installer (par exemple, `1.6.9~rc4`). |
| `-v, --version VERSION` | Spécifie la version de BunkerWeb à installer (par exemple, `1.6.9`). |
| `-w, --enable-wizard` | Active l'assistant de configuration. |
| `-n, --no-wizard` | Désactive l'assistant d'installation. |
| `--api`, `--enable-api` | Active le service API (FastAPI) systemd (désactivé par défaut). |
@ -2098,7 +2098,7 @@ sudo ./install-bunkerweb.sh --yes
sudo ./install-bunkerweb.sh --worker --no-wizard
# Install a specific version
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
sudo ./install-bunkerweb.sh --version 1.6.9
# Manager setup with remote worker instances (instances required)
sudo ./install-bunkerweb.sh --manager --instances "192.168.1.10 192.168.1.11"
@ -2239,12 +2239,12 @@ Veuillez vous assurer que **NGINX 1.28.2 est installé avant d'installer BunkerW
export UI_WIZARD=no
```
Et enfin, installez BunkerWeb 1.6.9~rc4 :
Et enfin, installez BunkerWeb 1.6.9 :
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Pour empêcher la mise à jour des paquets NGINX et/ou BunkerWeb lors de l'exécution de `apt upgrade`, vous pouvez utiliser la commande suivante :
@ -2287,12 +2287,12 @@ Veuillez vous assurer que **NGINX 1.28.2 est installé avant d'installer BunkerW
export UI_WIZARD=no
```
Et enfin, installez BunkerWeb 1.6.9~rc4 :
Et enfin, installez BunkerWeb 1.6.9 :
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
Pour empêcher la mise à jour des paquets NGINX et/ou BunkerWeb lors de l'exécution de `apt upgrade`, vous pouvez utiliser la commande suivante :
@ -2323,12 +2323,12 @@ Veuillez vous assurer que **NGINX 1.28.2 est installé avant d'installer BunkerW
export UI_WIZARD=no
```
Et enfin, installez BunkerWeb 1.6.9~rc4 :
Et enfin, installez BunkerWeb 1.6.9 :
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf makecache && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Pour empêcher la mise à jour des paquets NGINX et/ou BunkerWeb lors de l'exécution de `dnf upgrade`, vous pouvez utiliser la commande suivante :
@ -2373,12 +2373,12 @@ Veuillez vous assurer que **NGINX 1.28.2 est installé avant d'installer BunkerW
export UI_WIZARD=no
```
Enfin, installez BunkerWeb 1.6.9~rc4 :
Enfin, installez BunkerWeb 1.6.9 :
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
Pour empêcher la mise à jour des paquets NGINX et/ou BunkerWeb lors de l'exécution de `dnf upgrade`, vous pouvez utiliser la commande suivante :
@ -2471,7 +2471,7 @@ En adoptant cette approche, vous pouvez profiter d'une reconfiguration en temps
L'intégration de Docker autoconf implique l'utilisation du **mode multisite**. Pour plus d'informations, reportez-vous à la [section multisite](concepts.md#multisite-mode) de la documentation.
!!! info "Backend de base de données"
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) du dépôt.
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) du dépôt.
Pour activer les mises à jour automatiques de la configuration, incluez un conteneur supplémentaire appelé `bw-autoconf` dans la pile. Ce conteneur héberge le service autoconf, qui gère les modifications de configuration dynamiques pour BunkerWeb.
@ -2485,7 +2485,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2500,7 +2500,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -2515,7 +2515,7 @@ services:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2698,13 +2698,13 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
- "bunkerweb.NAMESPACE=my-namespace" # Définir l'espace de noms pour l'instance BunkerWeb afin que le service autoconf puisse la détecter
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
...
NAMESPACES: "my-namespace my-other-namespace" # Écouter uniquement ces espaces de noms
@ -2755,7 +2755,7 @@ Pour une configuration optimale, il est recommandé de définir BunkerWeb en tan
Compte tenu de la présence de plusieurs instances BunkerWeb, il est nécessaire d'établir un magasin de données partagé implémenté en tant que [ service Redis](https://redis.io/) ou [Valkey](https://valkey.io/). Ce service sera utilisé par les instances pour mettre en cache et partager des données entre elles. Vous trouverez de plus amples informations sur les paramètres Redis/Valkey [ici](features.md#redis).
!!! info "Backend de base de données"
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) du dépôt.
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) du dépôt.
La configuration des backends de base de données en cluster est hors du périmètre de cette documentation.
@ -2870,7 +2870,7 @@ Le **controller BunkerWeb** découvre automatiquement les pods avec sidecars Bun
```yaml
controller:
enabled: true
tag: "1.6.9~rc4"
tag: "1.6.9"
```
2. Pour chaque sidecar, ajoutez :
@ -2963,7 +2963,7 @@ Dans votre fichier `values.yaml` du chart BunkerWeb, configurez la variable d'en
```yaml
scheduler:
tag: "1.6.9~rc4"
tag: "1.6.9"
extraEnvs:
- name: BUNKERWEB_INSTANCES
value: "http://app1-bunkerweb-workers.namespace.svc.cluster.local:5000 http://app2-bunkerweb-workers.namespace.svc.cluster.local:5000"
@ -3005,7 +3005,7 @@ spec:
# Sidecar BunkerWeb
- name: bunkerweb
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- containerPort: 8080 # Port HTTP exposé
- containerPort: 5000 # API interne (obligatoire)
@ -3249,7 +3249,7 @@ Pour ajouter une nouvelle application protégée par BunkerWeb :
#### Fichiers YAML complets
Au lieu d'utiliser la charte Helm, vous pouvez également utiliser les modèles YAML dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) du référentiel GitHub. Veuillez noter que nous vous recommandons vivement d'utiliser le tableau de barre à la place.
Au lieu d'utiliser la charte Helm, vous pouvez également utiliser les modèles YAML dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) du référentiel GitHub. Veuillez noter que nous vous recommandons vivement d'utiliser le tableau de barre à la place.
### Ressources d'entrée
@ -3397,7 +3397,7 @@ metadata:
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
imagePullPolicy: Always
env:
- name: NAMESPACES
@ -3571,11 +3571,11 @@ service:
# BunkerWeb settings
bunkerweb:
tag: 1.6.9~rc4
tag: 1.6.9
# Scheduler settings
scheduler:
tag: 1.6.9~rc4
tag: 1.6.9
extraEnvs:
# Enable real IP module to get real IP of clients
- name: USE_REAL_IP
@ -3583,11 +3583,11 @@ scheduler:
# Controller settings
controller:
tag: 1.6.9~rc4
tag: 1.6.9
# UI settings
ui:
tag: 1.6.9~rc4
tag: 1.6.9
```
Installez BunkerWeb avec des valeurs personnalisées :
@ -4208,7 +4208,7 @@ Pour une configuration optimale, il est recommandé de planifier le **service Bu
En ce qui concerne le volume de la base de données, la documentation ne spécifie pas d'approche spécifique. Le choix d'un dossier partagé ou d'un pilote spécifique pour le volume de base de données dépend de votre cas d'utilisation unique et est laissé à la disposition du lecteur.
!!! info "Backend de base de données"
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) du dépôt.
Veuillez noter que nos instructions supposent que vous utilisez MariaDB comme backend de base de données par défaut, tel que configuré par le `DATABASE_URI` paramètre. Cependant, nous comprenons que vous préférerez peut-être utiliser d'autres backends pour votre intégration Docker. Si c'est le cas, soyez assuré que d'autres backends de base de données sont toujours possibles. Pour plus d'informations, consultez les fichiers docker-compose dans le [dossier misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) du dépôt.
La configuration des backends de base de données en cluster est hors du périmètre de cette documentation.
@ -4222,7 +4222,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -4251,7 +4251,7 @@ services:
- "bunkerweb.INSTANCE=yes" # Mandatory label for the autoconf service to identify the BunkerWeb instance
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -4272,7 +4272,7 @@ services:
- "node.role == worker"
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
SWARM_MODE: "yes"
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Remember to set a stronger password for the database
@ -4424,7 +4424,7 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
deploy:
mode: global
@ -4436,7 +4436,7 @@ networks:
- "bunkerweb.NAMESPACE=my-namespace" # Set the namespace for the BunkerWeb instance
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
NAMESPACES: "my-namespace my-other-namespace" # Only listen to these namespaces
...

12
docs/fr/plugins.md
View file

@ -89,7 +89,7 @@ La première étape consiste à installer le plugin en plaçant ses fichiers dan
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -125,7 +125,7 @@ La première étape consiste à installer le plugin en plaçant ses fichiers dan
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -168,7 +168,7 @@ La première étape consiste à installer le plugin en plaçant ses fichiers dan
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- /shared/bw-plugins:/data/plugins
...
@ -215,7 +215,7 @@ La première étape consiste à installer le plugin en plaçant ses fichiers dan
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE
@ -255,7 +255,7 @@ La première étape consiste à installer le plugin en plaçant ses fichiers dan
!!! tip "Plugins existants"
Si la documentation n'est pas suffisante, vous pouvez consulter le code source existant des [plugins officiels](https://github.com/bunkerity/bunkerweb-plugins) et des [plugins core](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/common/core) (déjà inclus dans BunkerWeb mais ce sont des plugins, techniquement parlant).
Si la documentation n'est pas suffisante, vous pouvez consulter le code source existant des [plugins officiels](https://github.com/bunkerity/bunkerweb-plugins) et des [plugins core](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/common/core) (déjà inclus dans BunkerWeb mais ce sont des plugins, techniquement parlant).
À quoi ressemble la structure d'un plugin :
```
@ -560,7 +560,7 @@ end
!!! tip "Plus d'exemples"
Si vous souhaitez voir la liste complète des fonctions disponibles, vous pouvez consulter les fichiers présents dans le [répertoire lua](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/bw/lua/bunkerweb) du dépôt.
Si vous souhaitez voir la liste complète des fonctions disponibles, vous pouvez consulter les fichiers présents dans le [répertoire lua](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/bw/lua/bunkerweb) du dépôt.
### Emplois

34
docs/fr/quickstart-guide.md
View file

@ -18,7 +18,7 @@ Ce guide de démarrage rapide vous aidera à installer rapidement BunkerWeb et
Protéger les applications web existantes déjà accessibles avec le protocole HTTP(S) est l'objectif principal de BunkerWeb : il agira comme un [proxy inverse classique](https://en.wikipedia.org/wiki/Reverse_proxy) avec des fonctionnalités de sécurité supplémentaires.
Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) du dépôt pour obtenir des exemples concrets.
Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) du dépôt pour obtenir des exemples concrets.
## Configuration de base
@ -33,7 +33,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Par défaut, le conteneur expose :
@ -51,8 +51,8 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
```bash
# Download the script and its checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify the checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -90,7 +90,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
services:
bunkerweb:
# This is the name that will be used to identify the instance in the Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -103,7 +103,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
@ -120,7 +120,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
restart: "unless-stopped"
@ -187,7 +187,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -203,7 +203,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -221,7 +221,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bw-docker
environment:
@ -244,7 +244,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-docker
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
@ -339,7 +339,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -369,7 +369,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- "bunkerweb.INSTANCE=yes"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -387,7 +387,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
<<: *bw-ui-env
DOCKER_HOST: "tcp://bw-docker:2375"
@ -416,7 +416,7 @@ Consultez le [dossier examples](https://github.com/bunkerity/bunkerweb/tree/v1.6
- "node.role == manager"
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
@ -638,7 +638,7 @@ Vous pouvez maintenant vous connecter avec le compte administrateur que vous ave
-e "www.example.com_REVERSE_PROXY_HOST=http://myapp:8080" \
-e "www.example.com_REVERSE_PROXY_URL=/" \
# --- Include any other existing environment variables for UI, Redis, CrowdSec, etc. ---
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Votre conteneur d'application (`myapp`) et le conteneur `bunkerweb-aio` doivent être sur le même réseau Docker pour que BunkerWeb puisse y accéder en utilisant le nom d'hôte `myapp`.
@ -660,7 +660,7 @@ Vous pouvez maintenant vous connecter avec le compte administrateur que vous ave
-p 443:8443/tcp \
-p 443:8443/udp \
# ... (all other relevant environment variables as shown in the main example above) ...
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Assurez-vous de remplacer `myapp` par le nom réel ou l'adresse IP de votre conteneur d'application et `http://myapp:8080` par son adresse et son port corrects.

36
docs/fr/upgrading.md
View file

@ -25,16 +25,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -141,20 +141,20 @@
Exemples:
```bash
# Upgrade to 1.6.9~rc4 interactively (will prompt for backup)
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
# Upgrade to 1.6.9 interactively (will prompt for backup)
sudo ./install-bunkerweb.sh --version 1.6.9
# Non-interactive upgrade with automatic backup to custom directory
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --backup-dir /var/backups/bw-2025-01 -y
sudo ./install-bunkerweb.sh -v 1.6.9 --backup-dir /var/backups/bw-2025-01 -y
# Silent unattended upgrade (logs suppressed) – relies on default auto-backup
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 -y -q
sudo ./install-bunkerweb.sh -v 1.6.9 -y -q
# Perform a dry run (plan) without applying changes
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --dry-run
sudo ./install-bunkerweb.sh -v 1.6.9 --dry-run
# Upgrade skipping automatic backup (NOT recommended)
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --no-auto-backup -y
sudo ./install-bunkerweb.sh -v 1.6.9 --no-auto-backup -y
```
!!! warning "Sauter les sauvegardes"
@ -234,7 +234,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Pour empêcher le paquet BunkerWeb d'être mis à niveau lors de l'exécution de `apt upgrade`, vous pouvez utiliser la commande suivante :
@ -260,7 +260,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Pour empêcher le paquet BunkerWeb d'être mis à niveau lors de l'exécution de `dnf upgrade`, vous pouvez utiliser la commande suivante :
@ -657,16 +657,16 @@ Nous avons ajouté une fonctionnalité d**'espace de noms** aux intégrations au
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -701,7 +701,7 @@ Nous avons ajouté une fonctionnalité d**'espace de noms** aux intégrations au
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
Pour empêcher le paquet BunkerWeb d'être mis à niveau lors de l'exécution de `apt upgrade`, vous pouvez utiliser la commande suivante :
@ -727,7 +727,7 @@ Nous avons ajouté une fonctionnalité d**'espace de noms** aux intégrations au
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
Pour empêcher le paquet BunkerWeb d'être mis à niveau lors de l'exécution de `dnf upgrade`, vous pouvez utiliser la commande suivante :

8
docs/fr/web-ui.md
View file

@ -35,7 +35,7 @@ L’UI attend que le scheduler/l’API BunkerWeb/le redis/la base soient accessi
Utilisez les images publiées et le layout du [guide de démarrage rapide](quickstart-guide.md#__tabbed_1_3) pour monter la stack, puis terminez la configuration dans le navigateur.
```bash
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9~rc4-rc1/misc/integrations/docker-compose.yml up -d
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9-rc1/misc/integrations/docker-compose.yml up -d
```
Ouvrez le nom d’hôte du scheduler (par ex. `https://www.example.com/changeme`) et lancez l’assistant `/setup` pour configurer l’UI, le scheduler et l’instance.
@ -52,7 +52,7 @@ L’UI attend que le scheduler/l’API BunkerWeb/le redis/la base soient accessi
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -63,7 +63,7 @@ L’UI attend que le scheduler/l’API BunkerWeb/le redis/la base soient accessi
networks: [bw-universe, bw-services]
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *service-env
BUNKERWEB_INSTANCES: "bunkerweb"
@ -83,7 +83,7 @@ L’UI attend que le scheduler/l’API BunkerWeb/le redis/la base soient accessi
networks: [bw-universe, bw-db]
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *service-env
ADMIN_USERNAME: "admin"

108
docs/integrations.md
View file

@ -1268,7 +1268,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
By default, the container exposes:
@ -1294,7 +1294,7 @@ A named volume (or bind mount) is required to persist the SQLite database, cache
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1366,7 +1366,7 @@ docker run -d \
-e API_PASSWORD=StrongP@ssw0rd \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
-p 8888:8888/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Recommended (behind BunkerWeb) — do not publish `8888`; reverse‑proxy it instead:
@ -1374,7 +1374,7 @@ Recommended (behind BunkerWeb) — do not publish `8888`; reverse‑proxy it ins
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1446,7 +1446,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* When `USE_CROWDSEC=yes`, the entrypoint will:
@ -1501,7 +1501,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
!!! info "How it works internally"
@ -1523,7 +1523,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Notes:
@ -1559,7 +1559,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* **Local registration** is skipped when `CROWDSEC_API` is not `127.0.0.1` or `localhost`.
@ -1593,13 +1593,13 @@ By accessing these prebuilt images from Docker Hub, you can quickly pull and run
Whether you're conducting tests, developing applications, or deploying BunkerWeb in production, the Docker containerization option provides flexibility and ease of use. Embracing this method empowers you to take full advantage of BunkerWeb's features while leveraging the benefits of Docker technology.
```shell
docker pull bunkerity/bunkerweb:1.6.9-rc4
docker pull bunkerity/bunkerweb:1.6.9
```
Docker images are also available on [GitHub packages](https://github.com/orgs/bunkerity/packages?repo_name=bunkerweb) and can be downloaded using the `ghcr.io` repository address:
```shell
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9-rc4
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9
```
Key concepts for Docker integration include:
@ -1609,7 +1609,7 @@ Key concepts for Docker integration include:
- **Networks**: Docker networks play a vital role in the integration of BunkerWeb. These networks serve two main purposes: exposing ports to clients and connecting to upstream web services. By exposing ports, BunkerWeb can accept incoming requests from clients, allowing them to access the protected web services. Additionally, by connecting to upstream web services, BunkerWeb can efficiently route and manage traffic, providing enhanced security and performance.
!!! info "Database backend"
Please note that our instructions assume you are using SQLite as the default database backend, as configured by the `DATABASE_URI` setting. However, other database backends are also supported. See the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) of the repository for more information.
Please note that our instructions assume you are using SQLite as the default database backend, as configured by the `DATABASE_URI` setting. However, other database backends are also supported. See the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) of the repository for more information.
### Environment variables
@ -1619,7 +1619,7 @@ Settings are passed to the Scheduler using Docker environment variables:
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- MY_SETTING=value
- ANOTHER_SETTING=another value
@ -1663,7 +1663,7 @@ This ensures sensitive settings are kept out of the environment and logs.
The [scheduler](concepts.md#scheduler) runs in its own container, which is also available on Docker Hub:
```shell
docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
docker pull bunkerity/bunkerweb-scheduler:1.6.9
```
!!! info "BunkerWeb settings"
@ -1684,7 +1684,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
environment:
# This will set the API settings for the BunkerWeb container
<<: *bw-api-env
@ -1693,7 +1693,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
- bw-universe
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
# This will set the API settings for the Scheduler container
<<: *bw-api-env
@ -1711,7 +1711,7 @@ A volume is needed to store the SQLite database and backups used by the schedule
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- bw-storage:/data
...
@ -1857,7 +1857,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1870,7 +1870,7 @@ services:
- bw-universe
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@ -1903,7 +1903,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1916,7 +1916,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
environment:
@ -1982,8 +1982,8 @@ To get started, download the installation script and its checksum, then verify t
```bash
# Download the script and its checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify the checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -2042,7 +2042,7 @@ For non-interactive or automated setups, the script can be controlled with comma
| Option | Description |
| ----------------------- | --------------------------------------------------------------------- |
| `-v, --version VERSION` | Specifies the BunkerWeb version to install (e.g., `1.6.9~rc4`). |
| `-v, --version VERSION` | Specifies the BunkerWeb version to install (e.g., `1.6.9`). |
| `-w, --enable-wizard` | Enables the setup wizard. |
| `-n, --no-wizard` | Disables the setup wizard. |
| `-y, --yes` | Runs in non-interactive mode using default answers for all prompts. |
@ -2107,7 +2107,7 @@ sudo ./install-bunkerweb.sh --yes
sudo ./install-bunkerweb.sh --worker --no-wizard
# Install a specific version
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
sudo ./install-bunkerweb.sh --version 1.6.9
# Manager setup with remote worker instances (instances required)
sudo ./install-bunkerweb.sh --manager --instances "192.168.1.10 192.168.1.11"
@ -2281,12 +2281,12 @@ Please ensure that you have **NGINX 1.28.2 installed before installing BunkerWeb
export UI_WIZARD=no
```
And finally install BunkerWeb 1.6.9~rc4:
And finally install BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command:
@ -2329,12 +2329,12 @@ Please ensure that you have **NGINX 1.28.2 installed before installing BunkerWeb
export UI_WIZARD=no
```
And finally install BunkerWeb 1.6.9~rc4:
And finally install BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command:
@ -2365,12 +2365,12 @@ Please ensure that you have **NGINX 1.28.2 installed before installing BunkerWeb
export UI_WIZARD=no
```
And finally install BunkerWeb 1.6.9~rc4:
And finally install BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf makecache && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command:
@ -2415,12 +2415,12 @@ Please ensure that you have **NGINX 1.28.2 installed before installing BunkerWeb
export UI_WIZARD=no
```
And finally install BunkerWeb 1.6.9~rc4:
And finally install BunkerWeb 1.6.9:
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command:
@ -2513,7 +2513,7 @@ By adopting this approach, you can enjoy real-time reconfiguration of BunkerWeb
The Docker autoconf integration implies the use of **multisite mode**. Please refer to the [multisite section](concepts.md#multisite-mode) of the documentation for more information.
!!! info "Database backend"
Please be aware that our instructions assume you are using MariaDB as the default database backend, as configured by the `DATABASE_URI` setting. However, we understand that you may prefer to utilize alternative backends for your Docker integration. If that is the case, rest assured that other database backends are still possible. See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) of the repository for more information.
Please be aware that our instructions assume you are using MariaDB as the default database backend, as configured by the `DATABASE_URI` setting. However, we understand that you may prefer to utilize alternative backends for your Docker integration. If that is the case, rest assured that other database backends are still possible. See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) of the repository for more information.
To enable automated configuration updates, include an additional container called `bw-autoconf` in the stack. This container hosts the autoconf service, which manages dynamic configuration changes for BunkerWeb.
@ -2527,7 +2527,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2542,7 +2542,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -2557,7 +2557,7 @@ services:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2739,13 +2739,13 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
- "bunkerweb.NAMESPACE=my-namespace" # Set the namespace for the BunkerWeb instance so the autoconf service can detect it
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
...
NAMESPACES: "my-namespace my-other-namespace" # Only listen to these namespaces
@ -2805,7 +2805,7 @@ Further information about the Redis/Valkey settings can be found [here](features
as configured by the `DATABASE_URI` setting.
However, we understand that you may prefer to utilize alternative backends for your Docker integration.
If that is the case, rest assured that other database backends are still possible.
See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)
See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)
of the repository for more information.
Clustered database backends setup are out-of-the-scope of this documentation.
@ -2922,7 +2922,7 @@ The **BunkerWeb controller** automatically discovers pods with BunkerWeb sidecar
```yaml
controller:
enabled: true
tag: "1.6.9~rc4"
tag: "1.6.9"
```
2. For each sidecar, add:
@ -3015,7 +3015,7 @@ In your BunkerWeb chart `values.yaml`, configure the `BUNKERWEB_INSTANCES` envir
```yaml
scheduler:
tag: "1.6.9~rc4"
tag: "1.6.9"
extraEnvs:
- name: BUNKERWEB_INSTANCES
value: "http://app1-bunkerweb-workers.namespace.svc.cluster.local:5000 http://app2-bunkerweb-workers.namespace.svc.cluster.local:5000"
@ -3059,7 +3059,7 @@ spec:
# BunkerWeb Sidecar
- name: bunkerweb
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- containerPort: 8080 # Exposed HTTP port
- containerPort: 5000 # Internal API (mandatory)
@ -3330,7 +3330,7 @@ To add a new application protected by BunkerWeb:
#### Full YAML files
Instead of using the helm chart, you can also use the YAML boilerplates inside the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) of the GitHub repository. Please note that we highly recommend to use the helm chart instead.
Instead of using the helm chart, you can also use the YAML boilerplates inside the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) of the GitHub repository. Please note that we highly recommend to use the helm chart instead.
### Ingress resources
@ -3478,7 +3478,7 @@ metadata:
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
imagePullPolicy: Always
env:
- name: NAMESPACES
@ -3652,11 +3652,11 @@ service:
# BunkerWeb settings
bunkerweb:
tag: 1.6.9~rc4
tag: 1.6.9
# Scheduler settings
scheduler:
tag: 1.6.9~rc4
tag: 1.6.9
extraEnvs:
# Enable real IP module to get real IP of clients
- name: USE_REAL_IP
@ -3664,11 +3664,11 @@ scheduler:
# Controller settings
controller:
tag: 1.6.9~rc4
tag: 1.6.9
# UI settings
ui:
tag: 1.6.9~rc4
tag: 1.6.9
```
Install BunkerWeb with custom values:
@ -4289,7 +4289,7 @@ Since multiple instances of BunkerWeb are running, a shared data store implement
As for the database volume, the documentation does not specify a specific approach. Choosing either a shared folder or a specific driver for the database volume is dependent on your unique use-case and is left as an exercise for the reader.
!!! info "Database backend"
Please be aware that our instructions assume you are using MariaDB as the default database backend, as configured by the `DATABASE_URI` setting. However, we understand that you may prefer to utilize alternative backends for your Docker integration. If that is the case, rest assured that other database backends are still possible. See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) of the repository for more information.
Please be aware that our instructions assume you are using MariaDB as the default database backend, as configured by the `DATABASE_URI` setting. However, we understand that you may prefer to utilize alternative backends for your Docker integration. If that is the case, rest assured that other database backends are still possible. See docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) of the repository for more information.
Clustered database backends setup are out-of-the-scope of this documentation.
@ -4303,7 +4303,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -4332,7 +4332,7 @@ services:
- "bunkerweb.INSTANCE=yes" # Mandatory label for the autoconf service to identify the BunkerWeb instance
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@ -4353,7 +4353,7 @@ services:
- "node.role == worker"
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
SWARM_MODE: "yes"
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Remember to set a stronger password for the database
@ -4505,7 +4505,7 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
deploy:
mode: global
@ -4517,7 +4517,7 @@ networks:
- "bunkerweb.NAMESPACE=my-namespace" # Set the namespace for the BunkerWeb instance
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
NAMESPACES: "my-namespace my-other-namespace" # Only listen to these namespaces
...

12
docs/plugins.md
View file

@ -89,7 +89,7 @@ The first step is to install the plugin by placing its files inside the correspo
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -125,7 +125,7 @@ The first step is to install the plugin by placing its files inside the correspo
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -168,7 +168,7 @@ The first step is to install the plugin by placing its files inside the correspo
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- /shared/bw-plugins:/data/plugins
...
@ -215,7 +215,7 @@ The first step is to install the plugin by placing its files inside the correspo
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE
@ -255,7 +255,7 @@ The first step is to install the plugin by placing its files inside the correspo
!!! tip "Existing plugins"
If the documentation is not enough, you can have a look at the existing source code of [official plugins](https://github.com/bunkerity/bunkerweb-plugins) and the [core plugins](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/common/core) (already included in BunkerWeb but they are plugins, technically speaking).
If the documentation is not enough, you can have a look at the existing source code of [official plugins](https://github.com/bunkerity/bunkerweb-plugins) and the [core plugins](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/common/core) (already included in BunkerWeb but they are plugins, technically speaking).
What a plugin structure looks like:
```
@ -563,7 +563,7 @@ end
!!! tip "More examples"
If you want to see the full list of available functions, you can have a look at the files present in the [lua directory](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/bw/lua/bunkerweb) of the repository.
If you want to see the full list of available functions, you can have a look at the files present in the [lua directory](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/bw/lua/bunkerweb) of the repository.
### Jobs

34
docs/quickstart-guide.md
View file

@ -18,7 +18,7 @@ This quickstart guide will help you to quickly install BunkerWeb and secure a we
Protecting existing web applications already accessible with the HTTP(S) protocol is the main goal of BunkerWeb: it will act as a classical [reverse proxy](https://en.wikipedia.org/wiki/Reverse_proxy) with extra security features.
See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) of the repository to get real-world examples.
See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) of the repository to get real-world examples.
## Basic setup
@ -33,7 +33,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
By default, the container exposes:
@ -51,8 +51,8 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
```bash
# Download the script and its checksum
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# Verify the checksum
sha256sum -c install-bunkerweb.sh.sha256
@ -90,7 +90,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
services:
bunkerweb:
# This is the name that will be used to identify the instance in the Scheduler
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -103,7 +103,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
@ -120,7 +120,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
restart: "unless-stopped"
@ -187,7 +187,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -203,7 +203,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -221,7 +221,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bw-docker
environment:
@ -244,7 +244,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-docker
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
@ -339,7 +339,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -369,7 +369,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- "bunkerweb.INSTANCE=yes"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -387,7 +387,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
<<: *bw-ui-env
DOCKER_HOST: "tcp://bw-docker:2375"
@ -416,7 +416,7 @@ See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4
- "node.role == manager"
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
@ -638,7 +638,7 @@ You can now log in with the administrator account you created during the setup w
-e "www.example.com_REVERSE_PROXY_HOST=http://myapp:8080" \
-e "www.example.com_REVERSE_PROXY_URL=/" \
# --- Include any other existing environment variables for UI, Redis, CrowdSec, etc. ---
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Your application container (`myapp`) and the `bunkerweb-aio` container must be on the same Docker network for BunkerWeb to reach it using the hostname `myapp`.
@ -660,7 +660,7 @@ You can now log in with the administrator account you created during the setup w
-p 443:8443/tcp \
-p 443:8443/udp \
# ... (all other relevant environment variables as shown in the main example above) ...
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
Make sure to replace `myapp` with the actual name or IP of your application container and `http://myapp:8080` with its correct address and port.

36
docs/upgrading.md
View file

@ -25,16 +25,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -141,20 +141,20 @@
Examples:
```bash
# Upgrade to 1.6.9~rc4 interactively (will prompt for backup)
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
# Upgrade to 1.6.9 interactively (will prompt for backup)
sudo ./install-bunkerweb.sh --version 1.6.9
# Non-interactive upgrade with automatic backup to custom directory
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --backup-dir /var/backups/bw-2025-01 -y
sudo ./install-bunkerweb.sh -v 1.6.9 --backup-dir /var/backups/bw-2025-01 -y
# Silent unattended upgrade (logs suppressed) – relies on default auto-backup
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 -y -q
sudo ./install-bunkerweb.sh -v 1.6.9 -y -q
# Perform a dry run (plan) without applying changes
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --dry-run
sudo ./install-bunkerweb.sh -v 1.6.9 --dry-run
# Upgrade skipping automatic backup (NOT recommended)
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --no-auto-backup -y
sudo ./install-bunkerweb.sh -v 1.6.9 --no-auto-backup -y
```
!!! warning "Skipping backups"
@ -234,7 +234,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
To prevent the BunkerWeb package from upgrading when executing `apt upgrade`, you can use the following command :
@ -260,7 +260,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
To prevent the BunkerWeb package from upgrading when executing `dnf upgrade`, you can use the following command :
@ -657,16 +657,16 @@ We added a **namespace** feature to the autoconf integrations. Namespaces allow
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -701,7 +701,7 @@ We added a **namespace** feature to the autoconf integrations. Namespaces allow
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
To prevent the BunkerWeb package from upgrading when executing `apt upgrade`, you can use the following command :
@ -727,7 +727,7 @@ We added a **namespace** feature to the autoconf integrations. Namespaces allow
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
To prevent the BunkerWeb package from upgrading when executing `dnf upgrade`, you can use the following command :

6
docs/web-ui.md
View file

@ -47,7 +47,7 @@ The UI expects the scheduler/(BunkerWeb) API/redis/database stack to be reachabl
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -62,7 +62,7 @@ The UI expects the scheduler/(BunkerWeb) API/redis/database stack to be reachabl
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *service-env
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
@ -86,7 +86,7 @@ The UI expects the scheduler/(BunkerWeb) API/redis/database stack to be reachabl
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *service-env
ADMIN_USERNAME: "admin"

106
docs/zh/advanced.md
View file

@ -1,8 +1,8 @@
# 高级用法
GitHub 仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) 文件夹中提供了许多真实世界的用例示例。
GitHub 仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) 文件夹中提供了许多真实世界的用例示例。
我们还提供了许多样板文件，例如用于各种集成和数据库类型的 YAML 文件。这些都可以在 [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations) 文件夹中找到。
我们还提供了许多样板文件，例如用于各种集成和数据库类型的 YAML 文件。这些都可以在 [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations) 文件夹中找到。
本节仅关注高级用法和安全调整，请参阅文档的[功能部分](features.md)以查看所有可用的设置。
@ -85,7 +85,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请注意，如果您的容器已经创建，您需要删除并重新创建它，以便更新新的环境变量。
@ -96,7 +96,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -104,7 +104,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -121,7 +121,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -129,7 +129,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -176,7 +176,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -184,7 +184,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
REAL_IP_HEADER: "X-Forwarded-For"
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -249,7 +249,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请注意，如果您的容器已经创建，您需要删除并重新创建它，以便更新新的环境变量。
@ -260,7 +260,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -270,7 +270,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -288,7 +288,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -298,7 +298,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -350,7 +350,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
```yaml
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -360,7 +360,7 @@ BunkerWeb 实际上支持两种方法来检索客户端的真实 IP 地址：
...
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
USE_REAL_IP: "yes"
@ -485,8 +485,8 @@ Manager 是集群的大脑，运行 Scheduler、数据库以及可选的 Web 界
```bash
# 下载脚本及校验文件
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# 校验完整性
sha256sum -c install-bunkerweb.sh.sha256
@ -585,7 +585,7 @@ Manager 是集群的大脑，运行 Scheduler、数据库以及可选的 Web 界
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: "192.168.1.11 192.168.1.12" # 替换为 Worker IP
@ -604,7 +604,7 @@ Manager 是集群的大脑，运行 Scheduler、数据库以及可选的 Web 界
- bw-redis
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
ports:
- "7000:7000" # 暴露 UI 端口
environment:
@ -687,7 +687,7 @@ Worker 负责处理进入的流量。
```yaml title="docker-compose.yml"
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -992,7 +992,7 @@ systemctl status systemd-resolved
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1020,7 +1020,7 @@ systemctl status systemd-resolved
- bw-dns
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1031,7 +1031,7 @@ systemctl status systemd-resolved
- bw-dns
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
DNS_RESOLVERS: "dnsmasq"
@ -1145,7 +1145,7 @@ systemctl status systemd-resolved
}" \
-p 80:8080/tcp \
-p 443:8443/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请注意，如果您的容器已经创建，您需要删除并重新创建它，以便应用新的环境变量。
@ -1185,7 +1185,7 @@ systemctl status systemd-resolved
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Docker"
@ -1208,7 +1208,7 @@ systemctl status systemd-resolved
```yaml
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- |
CUSTOM_CONF_SERVER_HTTP_hello-world=
@ -1251,7 +1251,7 @@ systemctl status systemd-resolved
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1321,7 +1321,7 @@ systemctl status systemd-resolved
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -1550,7 +1550,7 @@ BunkerWeb 能够作为**通用的 UDP/TCP 反向代理**，让您可以保护任
-p 443:8443/udp \
-p 10000:10000/tcp \
-p 20000:20000/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请注意，如果您的容器已经创建，您需要删除并重新创建它，以便应用新的环境变量。
@ -1573,7 +1573,7 @@ BunkerWeb 能够作为**通用的 UDP/TCP 反向代理**，让您可以保护任
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # 如果您想在使用 http 挑战类型时使用 Let's Encrypt 自动化，请保留此项
- "10000:10000" # app1
@ -1588,7 +1588,7 @@ BunkerWeb 能够作为**通用的 UDP/TCP 反向代理**，让您可以保护任
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # 此设置是指定 BunkerWeb 实例所必需的
@ -1639,7 +1639,7 @@ BunkerWeb 能够作为**通用的 UDP/TCP 反向代理**，让您可以保护任
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080" # 如果您想在使用 http 挑战类型时使用 Let's Encrypt 自动化，请保留此项
- "10000:10000" # app1
@ -1869,7 +1869,7 @@ BunkerWeb 能够作为**通用的 UDP/TCP 反向代理**，让您可以保护任
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
# 如果您想在使用 http 挑战类型时使用 Let's Encrypt 自动化，请保留此项
- published: 80
@ -1999,7 +1999,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请注意，如果您的容器已经创建，您需要删除并重新创建它，以便应用新的环境变量。
@ -2043,7 +2043,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2058,7 +2058,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # 此设置是指定 BunkerWeb 实例所必需的
@ -2152,7 +2152,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
environment:
@ -2165,7 +2165,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "" # 我们不需要在这里指定 BunkerWeb 实例，因为它们由 autoconf 服务自动检测
@ -2180,7 +2180,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2420,7 +2420,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
volumes:
- /shared/www:/var/www/html
...
@ -2519,7 +2519,7 @@ BunkerWeb 支持使用外部或远程的 [PHP-FPM](https://www.php.net/manual/en
```yaml
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
USE_IPv6: "yes"
@ -2658,7 +2658,7 @@ LOG_LEVEL_1=error
services:
bunkerweb:
# 这将是用于在调度程序中识别实例的名称
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2671,7 +2671,7 @@ LOG_LEVEL_1=error
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # 确保设置正确的实例名称
@ -2688,7 +2688,7 @@ LOG_LEVEL_1=error
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
volumes:
@ -2823,7 +2823,7 @@ log {
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
logging:
driver: "json-file"
options:
@ -2932,7 +2932,7 @@ BunkerWeb 提供了许多安全功能，您可以通过[功能](features.md)进
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
如果容器已存在，请重新创建以应用新的环境变量。
@ -2943,7 +2943,7 @@ BunkerWeb 提供了许多安全功能，您可以通过[功能](features.md)进
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -2962,7 +2962,7 @@ BunkerWeb 提供了许多安全功能，您可以通过[功能](features.md)进
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3005,7 +3005,7 @@ BunkerWeb 提供了许多安全功能，您可以通过[功能](features.md)进
```yaml
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
environment:
HTTP_PROXY: "http://proxy.example.local:3128"
@ -3957,11 +3957,11 @@ BunkerWeb 模板使用 [lua-resty-template](https://github.com/bungle/lua-resty-
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
# ... 其他设置（自定义页面无需在此处设置环境变量）
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./templates:/custom_templates:ro
environment:
@ -4044,7 +4044,7 @@ BunkerWeb 模板使用 [lua-resty-template](https://github.com/bungle/lua-resty-
spec:
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
env:
- name: CUSTOM_ERROR_PAGE
value: "/custom_templates/error.html"

8
docs/zh/api.md
View file

@ -41,7 +41,7 @@ BunkerWeb API 是用于管理实例、服务、封禁、插件、任务和自定
services:
bunkerweb:
# 调度器识别实例的名称
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -54,7 +54,7 @@ BunkerWeb API 是用于管理实例、服务、封禁、插件、任务和自定
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # 确保填写正确的实例名
@ -76,7 +76,7 @@ BunkerWeb API 是用于管理实例、服务、封禁、插件、任务和自定
- bw-db
bw-api:
image: bunkerity/bunkerweb-api:1.6.9-rc4
image: bunkerity/bunkerweb-api:1.6.9
environment:
<<: *bw-env
API_USERNAME: "admin"
@ -143,7 +143,7 @@ BunkerWeb API 是用于管理实例、服务、封禁、插件、任务和自定
-e SERVICE_API=yes \
-e API_WHITELIST_IPS="127.0.0.0/8" \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
=== "Linux"

4
docs/zh/concepts.md
View file

@ -105,7 +105,7 @@ app3.example.com_USE_BAD_BEHAVIOR=no
!!! info "更进一步"
您将在文档的[高级用法](advanced.md)和仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) 目录中找到多站点模式的具体示例。
您将在文档的[高级用法](advanced.md)和仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) 目录中找到多站点模式的具体示例。
## 自定义配置 {#custom-configurations}
@ -126,7 +126,7 @@ BunkerWeb 的另一个不可或缺的组件是 ModSecurity Web 应用程序防
!!! info "更进一步"
您将在文档的[高级用法](advanced.md#custom-configurations)和仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples) 目录中找到自定义配置的具体示例。
您将在文档的[高级用法](advanced.md#custom-configurations)和仓库的 [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples) 目录中找到自定义配置的具体示例。
## 数据库

4
docs/zh/features.md
View file

@ -1732,7 +1732,7 @@ CrowdSec 是一种现代的开源安全引擎，它基于行为分析和社区
services:
bunkerweb:
# 这是将用于在调度器中识别实例的名称
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1749,7 +1749,7 @@ CrowdSec 是一种现代的开源安全引擎，它基于行为分析和社区
syslog-address: "udp://10.20.30.254:514" # syslog 服务的 IP 地址
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # 确保设置正确的实例名称

108
docs/zh/integrations.md
View file

@ -1268,7 +1268,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
默认情况下，容器暴露：
@ -1284,7 +1284,7 @@ docker run -d \
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
volumes:
- bw-storage:/data
...
@ -1361,7 +1361,7 @@ docker run -d \
-e API_PASSWORD=StrongP@ssw0rd \
-p 80:8080/tcp -p 443:8443/tcp -p 443:8443/udp \
-p 8888:8888/tcp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
推荐（在 BunkerWeb 之后）— 不要发布 `8888`；而是反向代理它：
@ -1369,7 +1369,7 @@ docker run -d \
```yaml
services:
bunkerweb-aio:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
container_name: bunkerweb-aio
ports:
- "80:8080/tcp"
@ -1441,7 +1441,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* 当 `USE_CROWDSEC=yes` 时，入口点将：
@ -1496,7 +1496,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
!!! info "内部工作原理"
@ -1518,7 +1518,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
注意：
@ -1554,7 +1554,7 @@ docker run -d \
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
* 当 `CROWDSEC_API` 不是 `127.0.0.1` 或 `localhost` 时，将跳过**本地注册**。
@ -1588,13 +1588,13 @@ docker run -d \
无论您是进行测试、开发应用程序还是在生产中部署 BunkerWeb，Docker 容器化选项都提供了灵活性和易用性。采用这种方法使您能够充分利用 BunkerWeb 的功能，同时利用 Docker 技术的优势。
```shell
docker pull bunkerity/bunkerweb:1.6.9-rc4
docker pull bunkerity/bunkerweb:1.6.9
```
Docker 镜像也可在 [GitHub packages](https://github.com/orgs/bunkerity/packages?repo_name=bunkerweb) 上找到，可以使用 `ghcr.io` 仓库地址下载：
```shell
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9-rc4
docker pull ghcr.io/bunkerity/bunkerweb:1.6.9
```
Docker 集成的关键概念包括：
@ -1604,7 +1604,7 @@ Docker 集成的关键概念包括：
- **网络**：Docker 网络在 BunkerWeb 的集成中扮演着至关重要的角色。这些网络有两个主要目的：向客户端公开端口以及连接到上游 Web 服务。通过公开端口，BunkerWeb 可以接受来自客户端的传入请求，允许他们访问受保护的 Web 服务。此外，通过连接到上游 Web 服务，BunkerWeb 可以高效地路由和管理流量，提供增强的安全性和性能。
!!! info "数据库后端"
请注意，我们的说明假设您正在使用 SQLite 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，也支持其他数据库后端。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)中的 docker-compose 文件。
请注意，我们的说明假设您正在使用 SQLite 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，也支持其他数据库后端。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)中的 docker-compose 文件。
### 环境变量
@ -1614,7 +1614,7 @@ Docker 集成的关键概念包括：
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
- MY_SETTING=value
- ANOTHER_SETTING=another value
@ -1655,7 +1655,7 @@ secrets:
[调度器](concepts.md#scheduler) 在其自己的容器中运行，该容器也可在 Docker Hub 上找到：
```shell
docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
docker pull bunkerity/bunkerweb-scheduler:1.6.9
```
!!! info "BunkerWeb 设置"
@ -1676,7 +1676,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
environment:
# 这将为 BunkerWeb 容器设置 API
<<: *bw-api-env
@ -1685,7 +1685,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
- bw-universe
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
# 这将为调度器容器设置 API
<<: *bw-api-env
@ -1703,7 +1703,7 @@ docker pull bunkerity/bunkerweb-scheduler:1.6.9-rc4
...
services:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- bw-storage:/data
...
@ -1849,7 +1849,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1862,7 +1862,7 @@ services:
- bw-universe
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-api-env
BUNKERWEB_INSTANCES: "bunkerweb" # 这个设置是强制性的，用来指定 BunkerWeb 实例
@ -1895,7 +1895,7 @@ x-bw-api-env: &bw-api-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -1908,7 +1908,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
environment:
@ -1974,8 +1974,8 @@ docker build -t bw-ui -f src/ui/Dockerfile .
```bash
# 下载脚本及其校验和
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# 验证校验和
sha256sum -c install-bunkerweb.sh.sha256
@ -2034,7 +2034,7 @@ sudo ./install-bunkerweb.sh
| 选项 | 描述 |
| ----------------------- | ------------------------------------------------ |
| `-v, --version VERSION` | 指定要安装的 BunkerWeb 版本（例如 `1.6.9~rc4`）。 |
| `-v, --version VERSION` | 指定要安装的 BunkerWeb 版本（例如 `1.6.9`）。 |
| `-w, --enable-wizard` | 启用设置向导。 |
| `-n, --no-wizard` | 禁用设置向导。 |
| `-y, --yes` | 以非交互模式运行，对所有提示使用默认答案。 |
@ -2099,7 +2099,7 @@ sudo ./install-bunkerweb.sh --yes
sudo ./install-bunkerweb.sh --worker --no-wizard
# 安装一个特定版本
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
sudo ./install-bunkerweb.sh --version 1.6.9
# 带有远程工作实例的管理器设置（需要 instances）
sudo ./install-bunkerweb.sh --manager --instances "192.168.1.10 192.168.1.11"
@ -2243,12 +2243,12 @@ sudo ./install-bunkerweb.sh --yes --api
export UI_WIZARD=no
```
最后安装 BunkerWeb 1.6.9~rc4：
最后安装 BunkerWeb 1.6.9：
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
要防止在执行 `apt upgrade` 时升级 NGINX 和/或 BunkerWeb 包，您可以使用以下命令：
@ -2291,12 +2291,12 @@ sudo ./install-bunkerweb.sh --yes --api
export UI_WIZARD=no
```
最后安装 BunkerWeb 1.6.9~rc4：
最后安装 BunkerWeb 1.6.9：
```shell
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
sudo apt update && \
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo -E apt install -y --allow-downgrades bunkerweb=1.6.9
```
要防止在执行 `apt upgrade` 时升级 NGINX 和/或 BunkerWeb 包，您可以使用以下命令：
@ -2327,12 +2327,12 @@ sudo ./install-bunkerweb.sh --yes --api
export UI_WIZARD=no
```
最后安装 BunkerWeb 1.6.9~rc4：
最后安装 BunkerWeb 1.6.9：
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf makecache && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
要防止在执行 `dnf upgrade` 时升级 NGINX 和/或 BunkerWeb 包，您可以使用以下命令：
@ -2377,12 +2377,12 @@ sudo ./install-bunkerweb.sh --yes --api
export UI_WIZARD=no
```
最后安装 BunkerWeb 1.6.9~rc4：
最后安装 BunkerWeb 1.6.9：
```shell
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
sudo dnf check-update && \
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo -E dnf install -y --allowerasing bunkerweb-1.6.9
```
要防止在执行 `dnf upgrade` 时升级 NGINX 和/或 BunkerWeb 包，您可以使用以下命令：
@ -2475,7 +2475,7 @@ export SERVICE_UI=yes
Docker 自动配置集成意味着使用**多站点模式**。有关更多信息，请参阅文档的[多站点部分](concepts.md#multisite-mode)。
!!! info "数据库后端"
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)中的 docker-compose 文件。
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)中的 docker-compose 文件。
要启用自动配置更新，请在堆栈中包含一个名为 `bw-autoconf` 的额外容器。此容器承载自动配置服务，该服务管理 BunkerWeb 的动态配置更改。
@ -2489,7 +2489,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -2504,7 +2504,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # 我们不需要在这里指定 BunkerWeb 实例，因为它们由自动配置服务自动检测
@ -2519,7 +2519,7 @@ services:
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bunkerweb
- bw-docker
@ -2702,13 +2702,13 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
labels:
- "bunkerweb.INSTANCE=yes"
- "bunkerweb.NAMESPACE=my-namespace" # 为 BunkerWeb 实例设置命名空间，以便自动配置服务可以检测到它
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
...
NAMESPACES: "my-namespace my-other-namespace" # 只监听这些命名空间
@ -2759,7 +2759,7 @@ autoconf 服务充当一个 [Ingress 控制器](https://kubernetes.io/docs/conce
鉴于存在多个 BunkerWeb 实例，有必要建立一个共享数据存储，实现为一个 [Redis](https://redis.io/) 或 [Valkey](https://valkey.io/) 服务。这些实例将利用该服务来缓存和共享彼此之间的数据。有关 Redis/Valkey 设置的更多信息，请参见[此处](features.md#redis)。
!!! info "数据库后端"
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)中的 docker-compose 文件。
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)中的 docker-compose 文件。
集群数据库后端的设置超出了本文档的范围。
@ -2874,7 +2874,7 @@ The **BunkerWeb controller** automatically discovers pods with BunkerWeb sidecar
```yaml
controller:
enabled: true
tag: "1.6.9~rc4"
tag: "1.6.9"
```
2. For each sidecar, add:
@ -2967,7 +2967,7 @@ In your BunkerWeb chart `values.yaml`, configure the `BUNKERWEB_INSTANCES` envir
```yaml
scheduler:
tag: "1.6.9~rc4"
tag: "1.6.9"
extraEnvs:
- name: BUNKERWEB_INSTANCES
value: "http://app1-bunkerweb-workers.namespace.svc.cluster.local:5000 http://app2-bunkerweb-workers.namespace.svc.cluster.local:5000"
@ -3011,7 +3011,7 @@ spec:
# BunkerWeb Sidecar
- name: bunkerweb
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- containerPort: 8080 # Exposed HTTP port
- containerPort: 5000 # Internal API (mandatory)
@ -3282,7 +3282,7 @@ To add a new application protected by BunkerWeb:
#### 完整的 YAML 文件
除了使用 helm chart，您还可以使用 GitHub 仓库中 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)内的 YAML 样板文件。请注意，我们强烈建议您改用 helm chart。
除了使用 helm chart，您还可以使用 GitHub 仓库中 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)内的 YAML 样板文件。请注意，我们强烈建议您改用 helm chart。
### Ingress 资源
@ -3430,7 +3430,7 @@ metadata:
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-controller
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
imagePullPolicy: Always
env:
- name: NAMESPACES
@ -3604,11 +3604,11 @@ service:
# BunkerWeb 设置
bunkerweb:
tag: 1.6.9~rc4
tag: 1.6.9
# 调度器设置
scheduler:
tag: 1.6.9~rc4
tag: 1.6.9
extraEnvs:
# 启用 real IP 模块以获取客户端的真实 IP
- name: USE_REAL_IP
@ -3616,11 +3616,11 @@ scheduler:
# 控制器设置
controller:
tag: 1.6.9~rc4
tag: 1.6.9
# UI 设置
ui:
tag: 1.6.9~rc4
tag: 1.6.9
```
使用自定义值安装 BunkerWeb：
@ -4242,7 +4242,7 @@ kubectl delete ingress <old-ingress> -n <namespace>
至于数据库卷，文档并未指定具体的方法。为数据库卷选择共享文件夹或特定驱动程序取决于您的独特用例，留给读者自行决定。
!!! info "数据库后端"
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/misc/integrations)中的 docker-compose 文件。
请注意，我们的说明假设您正在使用 MariaDB 作为默认的数据库后端，这是由 `DATABASE_URI` 设置配置的。但是，我们理解您可能更喜欢为您的 Docker 集成使用其他后端。如果是这样，请放心，其他数据库后端仍然是可行的。有关更多信息，请参阅仓库的 [misc/integrations 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/misc/integrations)中的 docker-compose 文件。
集群数据库后端的设置超出了本文档的范围。
@ -4256,7 +4256,7 @@ x-bw-env: &bw-env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -4285,7 +4285,7 @@ services:
- "bunkerweb.INSTANCE=yes" # autoconf 服务识别 BunkerWeb 实例的强制性标签
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "" # 我们不需要在这里指定 BunkerWeb 实例，因为它们由 autoconf 服务自动检测
@ -4306,7 +4306,7 @@ services:
- "node.role == worker"
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
SWARM_MODE: "yes"
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # 记得为数据库设置一个更强的密码
@ -4455,7 +4455,7 @@ networks:
...
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
deploy:
mode: global
@ -4467,7 +4467,7 @@ networks:
- "bunkerweb.NAMESPACE=my-namespace" # 为 BunkerWeb 实例设置命名空间
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
NAMESPACES: "my-namespace my-other-namespace" # 只监听这些命名空间
...

12
docs/zh/plugins.md
View file

@ -89,7 +89,7 @@ BunkerWeb 附带一个插件系统，可以轻松添加新功能。安装插件
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -125,7 +125,7 @@ BunkerWeb 附带一个插件系统，可以轻松添加新功能。安装插件
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- ./bw-data:/data
...
@ -168,7 +168,7 @@ BunkerWeb 附带一个插件系统，可以轻松添加新功能。安装插件
services:
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
volumes:
- /shared/bw-plugins:/data/plugins
...
@ -215,7 +215,7 @@ BunkerWeb 附带一个插件系统，可以轻松添加新功能。安装插件
serviceAccountName: sa-bunkerweb
containers:
- name: bunkerweb-scheduler
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
imagePullPolicy: Always
env:
- name: KUBERNETES_MODE
@ -255,7 +255,7 @@ BunkerWeb 附带一个插件系统，可以轻松添加新功能。安装插件
!!! tip "现有插件"
如果文档不够，您可以查看[官方插件](https://github.com/bunkerity/bunkerweb-plugins)和[核心插件](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/common/core)的现有源代码（已包含在 BunkerWeb 中，但从技术上讲它们是插件）。
如果文档不够，您可以查看[官方插件](https://github.com/bunkerity/bunkerweb-plugins)和[核心插件](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/common/core)的现有源代码（已包含在 BunkerWeb 中，但从技术上讲它们是插件）。
插件结构如下所示：
```
@ -560,7 +560,7 @@ end
!!! tip "更多示例"
如果您想查看可用函数的完整列表，可以查看仓库的 [lua 目录](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/src/bw/lua/bunkerweb)中存在的文件。
如果您想查看可用函数的完整列表，可以查看仓库的 [lua 目录](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/src/bw/lua/bunkerweb)中存在的文件。
### 作业

34
docs/zh/quickstart-guide.md
View file

@ -18,7 +18,7 @@
保护已经可以通过 HTTP(S) 协议访问的现有 Web 应用程序是 BunkerWeb 的主要目标：它将充当一个带有额外安全功能的经典[反向代理](https://en.wikipedia.org/wiki/Reverse_proxy)。
有关真实世界的示例，请参阅仓库的 [examples 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9-rc4/examples)。
有关真实世界的示例，请参阅仓库的 [examples 文件夹](https://github.com/bunkerity/bunkerweb/tree/v1.6.9/examples)。
## 基本设置
@ -33,7 +33,7 @@
-p 80:8080/tcp \
-p 443:8443/tcp \
-p 443:8443/udp \
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
默认情况下，容器暴露：
@ -51,8 +51,8 @@
```bash
# 下载脚本及其校验和
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9-rc4/install-bunkerweb.sh.sha256
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh
curl -fsSL -O https://github.com/bunkerity/bunkerweb/releases/download/v1.6.9/install-bunkerweb.sh.sha256
# 验证校验和
sha256sum -c install-bunkerweb.sh.sha256
@ -90,7 +90,7 @@
services:
bunkerweb:
# 这是将用于在调度器中识别实例的名称
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -103,7 +103,7 @@
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-env
BUNKERWEB_INSTANCES: "bunkerweb" # 确保设置正确的实例名称
@ -120,7 +120,7 @@
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-env
restart: "unless-stopped"
@ -187,7 +187,7 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -203,7 +203,7 @@
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -221,7 +221,7 @@
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
depends_on:
- bw-docker
environment:
@ -244,7 +244,7 @@
- bw-docker
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # 记得设置一个更强的密钥（请参阅先决条件部分）
@ -339,7 +339,7 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- published: 80
target: 8080
@ -369,7 +369,7 @@
- "bunkerweb.INSTANCE=yes"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *bw-ui-env
BUNKERWEB_INSTANCES: ""
@ -387,7 +387,7 @@
- bw-db
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
environment:
<<: *bw-ui-env
DOCKER_HOST: "tcp://bw-docker:2375"
@ -416,7 +416,7 @@
- "node.role == manager"
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *bw-ui-env
TOTP_ENCRYPTION_KEYS: "mysecret" # 记得设置一个更强的密钥（请参阅先决条件部分）
@ -638,7 +638,7 @@
-e "www.example.com_REVERSE_PROXY_HOST=http://myapp:8080" \
-e "www.example.com_REVERSE_PROXY_URL=/" \
# --- 包括任何其他现有的用于 UI、Redis、CrowdSec 等的环境变量 ---
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
您的应用程序容器 (`myapp`) 和 `bunkerweb-aio` 容器必须在同一个 Docker 网络上，以便 BunkerWeb 能够使用主机名 `myapp` 访问它。
@ -660,7 +660,7 @@
-p 443:8443/tcp \
-p 443:8443/udp \
# ... （如上主示例所示的所有其他相关环境变量）...
bunkerity/bunkerweb-all-in-one:1.6.9-rc4
bunkerity/bunkerweb-all-in-one:1.6.9
```
请确保将 `myapp` 替换为您的应用程序容器的实际名称或 IP，并将 `http://myapp:8080` 替换为其正确的地址和端口。

36
docs/zh/upgrading.md
View file

@ -25,16 +25,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -141,20 +141,20 @@
示例：
```bash
# 交互式升级到 1.6.9~rc4（会提示备份）
sudo ./install-bunkerweb.sh --version 1.6.9~rc4
# 交互式升级到 1.6.9（会提示备份）
sudo ./install-bunkerweb.sh --version 1.6.9
# 使用自动备份到自定义目录的非交互式升级
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --backup-dir /var/backups/bw-2025-01 -y
sudo ./install-bunkerweb.sh -v 1.6.9 --backup-dir /var/backups/bw-2025-01 -y
# 静默无人值守升级（抑制日志）– 依赖默认的自动备份
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 -y -q
sudo ./install-bunkerweb.sh -v 1.6.9 -y -q
# 执行一次空运行（计划）而不应用更改
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --dry-run
sudo ./install-bunkerweb.sh -v 1.6.9 --dry-run
# 跳过自动备份进行升级（不推荐）
sudo ./install-bunkerweb.sh -v 1.6.9~rc4 --no-auto-backup -y
sudo ./install-bunkerweb.sh -v 1.6.9 --no-auto-backup -y
```
!!! warning "跳过备份"
@ -234,7 +234,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
为了防止在执行 `apt upgrade` 时升级 BunkerWeb 软件包，您可以使用以下命令：
@ -260,7 +260,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
为了防止在执行 `dnf upgrade` 时升级 BunkerWeb 软件包，您可以使用以下命令：
@ -657,16 +657,16 @@
```yaml
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
...
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
...
bw-autoconf:
image: bunkerity/bunkerweb-autoconf:1.6.9-rc4
image: bunkerity/bunkerweb-autoconf:1.6.9
...
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
...
```
@ -701,7 +701,7 @@
```shell
sudo apt update && \
sudo apt install -y --allow-downgrades bunkerweb=1.6.9~rc4
sudo apt install -y --allow-downgrades bunkerweb=1.6.9
```
为了防止在执行 `apt upgrade` 时升级 BunkerWeb 软件包，您可以使用以下命令：
@ -727,7 +727,7 @@
```shell
sudo dnf makecache && \
sudo dnf install -y --allowerasing bunkerweb-1.6.9~rc4
sudo dnf install -y --allowerasing bunkerweb-1.6.9
```
为了防止在执行 `dnf upgrade` 时升级 BunkerWeb 软件包，您可以使用以下命令：

8
docs/zh/web-ui.md
View file

@ -35,7 +35,7 @@ UI 需要可访问的 scheduler /（BunkerWeb）API / redis / 数据库。
使用已发布镜像与[快速入门](quickstart-guide.md#__tabbed_1_3)的布局启动栈，然后在浏览器完成向导。
```bash
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9~rc4-rc1/misc/integrations/docker-compose.yml up -d
docker compose -f https://raw.githubusercontent.com/bunkerity/bunkerweb/v1.6.9-rc1/misc/integrations/docker-compose.yml up -d
```
访问 scheduler 主机名（如 `https://www.example.com/changeme`），运行 `/setup` 向导以配置 UI、scheduler 与实例。
@ -52,7 +52,7 @@ UI 需要可访问的 scheduler /（BunkerWeb）API / redis / 数据库。
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"
@ -63,7 +63,7 @@ UI 需要可访问的 scheduler /（BunkerWeb）API / redis / 数据库。
networks: [bw-universe, bw-services]
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
environment:
<<: *service-env
BUNKERWEB_INSTANCES: "bunkerweb"
@ -83,7 +83,7 @@ UI 需要可访问的 scheduler /（BunkerWeb）API / redis / 数据库。
networks: [bw-universe, bw-db]
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
environment:
<<: *service-env
ADMIN_USERNAME: "admin"

4
examples/authelia/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/authentik/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/behind-reverse-proxy/docker-compose.yml
View file

@ -6,7 +6,7 @@ x-env: &env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
environment:
<<: *env
@ -17,7 +17,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/bigbluebutton/docker-compose.yml
View file

@ -25,7 +25,7 @@ services:
...
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -40,7 +40,7 @@ services:
bw-universe:
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/cors/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -22,7 +22,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-cloudflare/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-desec/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-digitalocean/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-dnsimple/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-dnsmadeeasy/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-gehirn/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-google/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-linode/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-luadns/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-nsone/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-ovh/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-rfc2136/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-route53/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-sakuracloud/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/dns-scaleway/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/docker-configs/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/drupal/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/ghost/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/gogs/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/hardened/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
# dropping all capabilities
cap_drop:
@ -33,7 +33,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/jellyfin/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/joomla/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/load-balancer/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/magento/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/mattermost/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/mongo-express/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/moodle/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/nextcloud/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/passbolt/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/php-cookie-flags/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -22,7 +22,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/php-multisite/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -23,7 +23,7 @@ services:
- net-app2
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/php-singlesite/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -22,7 +22,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/prestashop/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/proxy-protocol/docker-compose.yml
View file

@ -8,7 +8,7 @@ x-env: &env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
environment:
<<: *env
@ -19,7 +19,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/radarr/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/redmine/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/reverse-proxy-multisite/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/reverse-proxy-singlesite/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/reverse-proxy-websocket/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

4
examples/stream-multisite/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080" # required to resolve let's encrypt challenges
@ -16,7 +16,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bunkerweb-scheduler
depends_on:
- bunkerweb

4
examples/syslog/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
depends_on:
- mysyslog
@ -21,7 +21,7 @@ services:
syslog-address: "udp://10.10.10.254:514"
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
depends_on:
- bunkerweb
- mysyslog

4
examples/tomcat/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bunkerweb-scheduler
depends_on:
- bunkerweb

4
examples/tor-hidden-service/docker-compose.yml
View file

@ -10,7 +10,7 @@ services:
- onion-net
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
environment:
API_WHITELIST_IP: "127.0.0.0/8 10.20.30.0/24"
@ -21,7 +21,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bunkerweb-scheduler
depends_on:
- bunkerweb

6
examples/web-ui/docker-compose.wizard.yml
View file

@ -3,7 +3,7 @@ x-env: &env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -17,7 +17,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb
@ -40,7 +40,7 @@ services:
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
container_name: bw-ui
environment:
<<: *env

6
examples/web-ui/docker-compose.yml
View file

@ -3,7 +3,7 @@ x-env: &env
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -17,7 +17,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb
@ -43,7 +43,7 @@ services:
- bw-db
bw-ui:
image: bunkerity/bunkerweb-ui:1.6.9-rc4
image: bunkerity/bunkerweb-ui:1.6.9
container_name: bw-ui
environment:
<<: *env

4
examples/wordpress/docker-compose.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb:
image: bunkerity/bunkerweb:1.6.9-rc4
image: bunkerity/bunkerweb:1.6.9
container_name: bunkerweb
ports:
- "80:8080/tcp"
@ -14,7 +14,7 @@ services:
- bw-services
bw-scheduler:
image: bunkerity/bunkerweb-scheduler:1.6.9-rc4
image: bunkerity/bunkerweb-scheduler:1.6.9
container_name: bw-scheduler
depends_on:
- bunkerweb

2
misc/install-bunkerweb.sh
View file

@ -14,7 +14,7 @@ NC='\033[0m' # No Color
# Default values
# Hardcoded default version (immutable reference)
DEFAULT_BUNKERWEB_VERSION="1.6.9~rc4"
DEFAULT_BUNKERWEB_VERSION="1.6.9"
# Mutable effective version (can be overridden by --version)
BUNKERWEB_VERSION="$DEFAULT_BUNKERWEB_VERSION"
NGINX_VERSION=""

2
misc/integrations/all-in-one.mariadb.ui.yml
View file

@ -1,6 +1,6 @@
services:
bunkerweb-all-in-one:
image: bunkerity/bunkerweb-all-in-one:1.6.9-rc4
image: bunkerity/bunkerweb-all-in-one:1.6.9
ports:
- "80:8080/tcp"
- "443:8443/tcp"

Some files were not shown because too many files have changed in this diff Show more