mirror of
https://github.com/bunkerity/bunkerweb
synced 2026-05-24 09:28:37 +00:00
feat: update version to 1.6.0-rc1 across project files and Docker configurations
This commit is contained in:
Théophile Diot
parent
9bc64d515d
commit
b3e273dd9a
39 changed files with 264 additions and 264 deletions
2
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
2
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
|
|
@ -47,7 +47,7 @@ body:
|
|||
label: BunkerWeb version
|
||||
description: What version of BunkerWeb are you running?
|
||||
placeholder: Version
|
||||
value: 1.6.0-beta
|
||||
value: 1.6.0-rc1
|
||||
validations:
|
||||
required: true
|
||||
- type: dropdown
|
||||
|
|
|
|||
84
README.md
84
README.md
|
|
@ -1,5 +1,5 @@
|
|||
<p align="center">
|
||||
<img alt="BunkerWeb logo" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/misc/logo.png" height=100 width=350 />
|
||||
<img alt="BunkerWeb logo" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/misc/logo.png" height=100 width=350 />
|
||||
</p>
|
||||
|
||||
<p align="center">
|
||||
|
|
@ -26,7 +26,7 @@
|
|||
|
|
||||
👨💻 <a href="https://demo.bunkerweb.io/?utm_campaign=self&utm_source=github">Demo</a>
|
||||
|
|
||||
🛡️ <a href="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/examples">Examples</a>
|
||||
🛡️ <a href="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/examples">Examples</a>
|
||||
|
|
||||
💬 <a href="https://discord.com/invite/fTf46FmtyD">Chat</a>
|
||||
|
|
||||
|
|
@ -44,14 +44,14 @@
|
|||
# BunkerWeb
|
||||
|
||||
<p align="center">
|
||||
<img alt="Overview banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/intro-overview.svg" />
|
||||
<img alt="Overview banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/docs/assets/img/intro-overview.svg" />
|
||||
</p>
|
||||
|
||||
BunkerWeb is a next-generation and 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.0-beta/integrations/?utm_campaign=self&utm_source=github#linux), [Docker](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#docker), [Swarm](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#swarm), [Kubernetes](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#kubernetes), …) and is fully configurable (don't panic, there is an [awesome web UI](https://docs.bunkerweb.io/1.6.0-beta/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 more 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.0-rc1/integrations/?utm_campaign=self&utm_source=github#linux), [Docker](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#docker), [Swarm](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#swarm), [Kubernetes](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#kubernetes), …) and is fully configurable (don't panic, there is an [awesome web UI](https://docs.bunkerweb.io/1.6.0-rc1/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 more a hassle.
|
||||
|
||||
BunkerWeb contains primary [security features](https://docs.bunkerweb.io/1.6.0-beta/security-tuning/?utm_campaign=self&utm_source=github) as part of the core but can be easily extended with additional ones thanks to a [plugin system](https://docs.bunkerweb.io/1.6.0-beta/plugins/?utm_campaign=self&utm_source=github).
|
||||
BunkerWeb contains primary [security features](https://docs.bunkerweb.io/1.6.0-rc1/security-tuning/?utm_campaign=self&utm_source=github) as part of the core but can be easily extended with additional ones thanks to a [plugin system](https://docs.bunkerweb.io/1.6.0-rc1/plugins/?utm_campaign=self&utm_source=github).
|
||||
|
||||
## Why BunkerWeb ?
|
||||
|
||||
|
|
@ -76,7 +76,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.0-beta/security-tuning/?utm_campaign=self&utm_source=github) section of the documentation.
|
||||
Learn more about the core security features in the [security tuning](https://docs.bunkerweb.io/1.6.0-rc1/security-tuning/?utm_campaign=self&utm_source=github) section of the documentation.
|
||||
|
||||
## Demo
|
||||
|
||||
|
|
@ -105,13 +105,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 supervision, the BunkerWeb PRO version will allow you to fully benefit from BunkerWeb and respond to your professional needs.
|
||||
|
||||
Be it in the documentation or the user interface, the PRO features are annotated with a crown <img src="https://docs.bunkerweb.io/1.6.0-beta/assets/img/pro-icon.svg" alt="crow pro icon" height="24px" width="24px"> to distinguish them from those integrated into the open-source version.
|
||||
Be it in the documentation or the user interface, the PRO features are annotated with a crown <img src="https://docs.bunkerweb.io/1.6.0-rc1/assets/img/pro-icon.svg" alt="crow pro icon" height="24px" width="24px"> 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 you want. The process is pretty straightforward :
|
||||
|
||||
- Claim your [free trial on the BunkerWeb panel](https://panel.bunkerweb.io/?utm_campaign=self&utm_source=doc)
|
||||
- Once connected to the client area, copy your PRO license key
|
||||
- Paste your private key into BunkerWeb using the [web UI](https://docs.bunkerweb.io/1.6.0-beta/web-ui/#upgrade-to-pro) or [specific setting](https://docs.bunkerweb.io/1.6.0-beta/settings/#pro)
|
||||
- Paste your private key into BunkerWeb using the [web UI](https://docs.bunkerweb.io/1.6.0-rc1/web-ui/#upgrade-to-pro) or [specific setting](https://docs.bunkerweb.io/1.6.0-rc1/settings/#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 question regarding the PRO version.
|
||||
|
||||
|
|
@ -144,10 +144,10 @@ Community and social networks :
|
|||
# Concepts
|
||||
|
||||
<p align="center">
|
||||
<img alt="Concepts banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/concepts.svg" />
|
||||
<img alt="Concepts banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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.0-beta/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.0-rc1/concepts/?utm_campaign=self&utm_source=github).
|
||||
|
||||
## Integrations
|
||||
|
||||
|
|
@ -155,12 +155,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.0-beta/integrations/?utm_campaign=self&utm_source=github#docker)
|
||||
- [Linux](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#linux)
|
||||
- [Docker autoconf](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#docker-autoconf)
|
||||
- [Kubernetes](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#kubernetes)
|
||||
- [Swarm](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#swarm)
|
||||
- [Microsoft Azure](https://docs.bunkerweb.io/1.6.0-beta/integrations/?utm_campaign=self&utm_source=github#microsoft-azure)
|
||||
- [Docker](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#docker)
|
||||
- [Linux](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#linux)
|
||||
- [Docker autoconf](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#docker-autoconf)
|
||||
- [Kubernetes](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#kubernetes)
|
||||
- [Swarm](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#swarm)
|
||||
- [Microsoft Azure](https://docs.bunkerweb.io/1.6.0-rc1/integrations/?utm_campaign=self&utm_source=github#microsoft-azure)
|
||||
|
||||
## Settings
|
||||
|
||||
|
|
@ -192,7 +192,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.0-beta/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.0-rc1/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).
|
||||
|
||||
|
|
@ -201,7 +201,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.0-beta/docs/assets/img/bunkerweb_db.svg" />
|
||||
<img alt="Database model" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/docs/assets/img/bunkerweb_db.svg" />
|
||||
</p>
|
||||
|
||||
State of the current configuration of BunkerWeb is stored in a backend database which contains the following data :
|
||||
|
|
@ -230,7 +230,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.0-beta/docs/assets/img/bunkerweb-cloud.webp" />
|
||||
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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 a like a BunkerWeb-as-a-Service !
|
||||
|
|
@ -240,7 +240,7 @@ You will find more information about BunkerWeb Cloud beta [here](https://www.bun
|
|||
## Docker
|
||||
|
||||
<p align="center">
|
||||
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/integration-docker.svg" />
|
||||
<img alt="Docker banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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).
|
||||
|
|
@ -251,46 +251,46 @@ 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.0-beta/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.0-rc1/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.0-beta/docs/assets/img/integration-autoconf.svg" />
|
||||
<img alt="Docker autoconf banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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.0-beta/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.0-rc1/integrations/?utm_campaign=self&utm_source=github#docker-autoconf) of the documentation.
|
||||
|
||||
## Swarm
|
||||
|
||||
<p align="center">
|
||||
<img alt="Swarm banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/integration-swarm.svg" />
|
||||
<img alt="Swarm banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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.0-beta/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.0-rc1/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.0-beta/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.0-rc1/integrations/?utm_campaign=self&utm_source=github#swarm) of the documentation.
|
||||
|
||||
## Kubernetes
|
||||
|
||||
<p align="center">
|
||||
<img alt="Kubernetes banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/integration-kubernetes.svg" />
|
||||
<img alt="Kubernetes banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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.
|
||||
|
||||
You will find more information in the [Kubernetes section](https://docs.bunkerweb.io/1.6.0-beta/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.0-rc1/integrations/?utm_campaign=self&utm_source=github#kubernetes) of the documentation.
|
||||
|
||||
## Linux
|
||||
|
||||
<p align="center">
|
||||
<img alt="Linux banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/integration-linux.svg" />
|
||||
<img alt="Linux banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/docs/assets/img/integration-linux.svg" />
|
||||
</p>
|
||||
|
||||
List of supported Linux distros :
|
||||
|
|
@ -307,16 +307,16 @@ You will find more information in the [Linux section](https://docs.bunkerweb.io/
|
|||
## Microsoft Azure
|
||||
|
||||
<p align="center">
|
||||
<img alt="Azure banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/integration-azure.webp" />
|
||||
<img alt="Azure banner" src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/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 a ARM template is available in the [misc folder](https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/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 a ARM template is available in the [misc folder](https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/misc/integrations/azure-arm-template.json).
|
||||
|
||||
You will find more information in the [Microsoft Azure section](https://docs.bunkerweb.io/1.6.0-beta/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.0-rc1/integrations/?utm_campaign=self&utm_source=github#microsoft-azure) of the documentation.
|
||||
|
||||
# Quickstart guide
|
||||
|
||||
Once you have setup BunkerWeb with the integration of your choice, you can follow the [quickstart guide](https://docs.bunkerweb.io/1.6.0-beta/quickstart-guide/?utm_campaign=self&utm_source=github) that will cover the following common use cases :
|
||||
Once you have setup BunkerWeb with the integration of your choice, you can follow the [quickstart guide](https://docs.bunkerweb.io/1.6.0-rc1/quickstart-guide/?utm_campaign=self&utm_source=github) that will cover the following common use cases :
|
||||
|
||||
- Protecting a single HTTP application
|
||||
- Protecting multiple HTTP application
|
||||
|
|
@ -327,9 +327,9 @@ Once you have setup BunkerWeb with the integration of your choice, you can follo
|
|||
|
||||
# Security tuning
|
||||
|
||||
BunkerWeb offers many security features that you can configure with [settings](https://docs.bunkerweb.io/1.6.0-beta/settings/?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 [settings](https://docs.bunkerweb.io/1.6.0-rc1/settings/?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.0-beta/security-tuning/?utm_campaign=self&utm_source=github) of the documentation.
|
||||
You will find more information in the [security tuning section](https://docs.bunkerweb.io/1.6.0-rc1/security-tuning/?utm_campaign=self&utm_source=github) of the documentation.
|
||||
|
||||
# Settings
|
||||
|
||||
|
|
@ -339,13 +339,13 @@ 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 suffix 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 [settings section](https://docs.bunkerweb.io/1.6.0-beta/settings/?utm_campaign=self&utm_source=github) of the documentation to get the full list.
|
||||
Check the [settings section](https://docs.bunkerweb.io/1.6.0-rc1/settings/?utm_campaign=self&utm_source=github) of the documentation to get the full list.
|
||||
|
||||
# Web UI
|
||||
|
||||
<p align="center">
|
||||
<a href="https://www.youtube.com/watch?v=Ao20SfvQyr4">
|
||||
<img src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-beta/docs/assets/img/user_interface_demo.webp" height="300" />
|
||||
<img src="https://github.com/bunkerity/bunkerweb/raw/v1.6.0-rc1/docs/assets/img/user_interface_demo.webp" height="300" />
|
||||
</a>
|
||||
</p>
|
||||
|
||||
|
|
@ -359,7 +359,7 @@ The "Web UI" is a web application that helps you manage your BunkerWeb instance
|
|||
- Monitor jobs execution
|
||||
- View the logs and search pattern
|
||||
|
||||
You will find more information in the [Web UI section](https://docs.bunkerweb.io/1.6.0-beta/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.0-rc1/web-ui/?utm_campaign=self&utm_source=github) of the documentation.
|
||||
|
||||
# Plugins
|
||||
|
||||
|
|
@ -377,7 +377,7 @@ Here is the list of "official" plugins that we maintain (see the [bunkerweb-plug
|
|||
| **VirusTotal** | 1.6 | 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.6 | 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.0-beta/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.0-rc1/plugins/?utm_campaign=self&utm_source=github) of the documentation.
|
||||
|
||||
# Support
|
||||
|
||||
|
|
@ -400,15 +400,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.0-beta/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.0-rc1/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.0-beta/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.0-rc1/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.0-beta/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.0-rc1/SECURITY.md) for more information.
|
||||
|
||||
# Star History
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ app3.example.com_USE_BAD_BEHAVIOR=no
|
|||
|
||||
!!! info "Going further"
|
||||
|
||||
You will find concrete examples of multisite mode in the [quickstart guide](quickstart-guide.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/examples) directory of the repository.
|
||||
You will find concrete examples of multisite mode in the [quickstart guide](quickstart-guide.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/examples) directory of the repository.
|
||||
|
||||
## Custom configurations
|
||||
|
||||
|
|
@ -97,7 +97,7 @@ By leveraging custom configurations, you unlock a world of possibilities to tail
|
|||
|
||||
!!! info "Going further"
|
||||
|
||||
You will find concrete examples of custom configurations in the [quickstart guide](quickstart-guide.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/examples) directory of the repository.
|
||||
You will find concrete examples of custom configurations in the [quickstart guide](quickstart-guide.md) of the documentation and the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/examples) directory of the repository.
|
||||
|
||||
## Database
|
||||
|
||||
|
|
|
|||
|
|
@ -35,13 +35,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.0-beta
|
||||
docker pull bunkerity/bunkerweb:1.6.0-rc1
|
||||
```
|
||||
|
||||
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.0-beta
|
||||
docker pull ghcr.io/bunkerity/bunkerweb:1.6.0-rc1
|
||||
```
|
||||
|
||||
Alternatively, if you prefer a more hands-on approach, you have the option to build the Docker image directly from the [source](https://github.com/bunkerity/bunkerweb). Building the image from source gives you greater control and customization over the deployment process. However, please note that this method may take some time to complete, depending on your hardware configuration.
|
||||
|
|
@ -71,7 +71,7 @@ When integrating BunkerWeb with Docker, there are key concepts to keep in mind,
|
|||
- **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 the traffic, providing enhanced security and performance.
|
||||
|
||||
!!! info "Database backend"
|
||||
Please be aware that our instructions assume you are using SQLite 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.0-beta/misc/integrations) folder of the repository for more information.
|
||||
Please be aware that our instructions assume you are using SQLite 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.0-rc1/misc/integrations) folder of the repository for more information.
|
||||
|
||||
### Environment variables
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ Settings are passed to the Scheduler using Docker environment variables :
|
|||
...
|
||||
services:
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
- MY_SETTING=value
|
||||
- ANOTHER_SETTING=another value
|
||||
|
|
@ -96,7 +96,7 @@ services:
|
|||
The [scheduler](concepts.md#scheduler) is executed in its own container which is also available on Docker Hub :
|
||||
|
||||
```shell
|
||||
docker pull bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
docker pull bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
```
|
||||
|
||||
Alternatively, you can build the Docker image directly from the [source](https://github.com/bunkerity/bunkerweb) (less coffee ☕ needed than the BunkerWeb image) :
|
||||
|
|
@ -123,7 +123,7 @@ docker build -t my-scheduler -f src/scheduler/Dockerfile .
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
environment:
|
||||
# This will set the API settings for the BunkerWeb container
|
||||
<<: *bw-api-env
|
||||
|
|
@ -132,7 +132,7 @@ docker build -t my-scheduler -f src/scheduler/Dockerfile .
|
|||
- bw-universe
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
# This will set the API settings for the Scheduler container
|
||||
<<: *bw-api-env
|
||||
|
|
@ -149,7 +149,7 @@ A volume is needed to store the SQLite database that will be used by the schedul
|
|||
...
|
||||
services:
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- bw-data:/data
|
||||
...
|
||||
|
|
@ -230,7 +230,7 @@ x-bw-api-env: &bw-api-env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -243,7 +243,7 @@ services:
|
|||
- bw-universe
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-api-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
|
||||
|
|
@ -271,7 +271,7 @@ x-bw-api-env: &bw-api-env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -284,7 +284,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
environment:
|
||||
|
|
@ -363,12 +363,12 @@ Please ensure that you have **NGINX 1.26.2 installed before installing BunkerWeb
|
|||
export UI_WIZARD=no
|
||||
```
|
||||
|
||||
And finally install BunkerWeb 1.6.0-beta :
|
||||
And finally install BunkerWeb 1.6.0-rc1 :
|
||||
|
||||
```shell
|
||||
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
|
||||
sudo apt update && \
|
||||
sudo -E apt install -y bunkerweb=1.6.0-beta
|
||||
sudo -E apt install -y bunkerweb=1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command :
|
||||
|
|
@ -411,12 +411,12 @@ Please ensure that you have **NGINX 1.26.2 installed before installing BunkerWeb
|
|||
export UI_WIZARD=no
|
||||
```
|
||||
|
||||
And finally install BunkerWeb 1.6.0-beta :
|
||||
And finally install BunkerWeb 1.6.0-rc1 :
|
||||
|
||||
```shell
|
||||
curl -s https://repo.bunkerweb.io/install/script.deb.sh | sudo bash && \
|
||||
sudo apt update && \
|
||||
sudo -E apt install -y bunkerweb=1.6.0-beta
|
||||
sudo -E apt install -y bunkerweb=1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading NGINX and/or BunkerWeb packages when executing `apt upgrade`, you can use the following command :
|
||||
|
|
@ -447,14 +447,14 @@ Please ensure that you have **NGINX 1.26.2 installed before installing BunkerWeb
|
|||
export UI_WIZARD=no
|
||||
```
|
||||
|
||||
And finally install BunkerWeb 1.6.0-beta :
|
||||
And finally install BunkerWeb 1.6.0-rc1 :
|
||||
|
||||
```shell
|
||||
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | \
|
||||
sed 's/yum install -y pygpgme --disablerepo='\''bunkerity_bunkerweb'\''/yum install -y python-gnupg/g' | \
|
||||
sed 's/pypgpme_check=`rpm -qa | grep -qw pygpgme`/python-gnupg_check=`rpm -qa | grep -qw python-gnupg`/g' | sudo bash && \
|
||||
sudo dnf makecache && \
|
||||
sudo -E dnf install -y bunkerweb-1.6.0-beta
|
||||
sudo -E dnf install -y bunkerweb-1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command :
|
||||
|
|
@ -499,13 +499,13 @@ Please ensure that you have **NGINX 1.26.2 installed before installing BunkerWeb
|
|||
export UI_WIZARD=no
|
||||
```
|
||||
|
||||
And finally install BunkerWeb 1.6.0-beta :
|
||||
And finally install BunkerWeb 1.6.0-rc1 :
|
||||
|
||||
```shell
|
||||
sudo dnf install -y epel-release && \
|
||||
curl -s https://repo.bunkerweb.io/install/script.rpm.sh | sudo bash && \
|
||||
sudo dnf check-update && \
|
||||
sudo -E dnf install -y bunkerweb-1.6.0-beta
|
||||
sudo -E dnf install -y bunkerweb-1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading NGINX and/or BunkerWeb packages when executing `dnf upgrade`, you can use the following command :
|
||||
|
|
@ -553,7 +553,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.0-beta/misc/integrations) folder 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.0-rc1/misc/integrations) folder 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.
|
||||
|
||||
|
|
@ -567,7 +567,7 @@ x-bw-env: &bw-env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -582,7 +582,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-env
|
||||
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
|
||||
|
|
@ -597,7 +597,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -682,7 +682,7 @@ networks:
|
|||
|
||||
### Namespaces
|
||||
|
||||
Starting from version `1.6.0-beta`, BunkerWeb's Autoconf stacks now support namespaces. This feature enables you to manage multiple "*clusters*" of BunkerWeb instances and services on the same Docker host. To take advantage of namespaces, simply set the `NAMESPACE` label on your services. Here's an example:
|
||||
Starting from version `1.6.0-rc1`, BunkerWeb's Autoconf stacks now support namespaces. This feature enables you to manage multiple "*clusters*" of BunkerWeb instances and services on the same Docker host. To take advantage of namespaces, simply set the `NAMESPACE` label on your services. Here's an example:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
|
|
@ -709,13 +709,13 @@ networks:
|
|||
...
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
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.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
...
|
||||
NAMESPACES: "my-namespace my-other-namespace" # Only listen to these namespaces
|
||||
|
|
@ -744,7 +744,7 @@ For an optimal setup, it is recommended to define BunkerWeb as a **[DaemonSet](h
|
|||
Given the presence of multiple BunkerWeb instances, it is necessary to establish a shared data store implemented as a [Redis](https://redis.io/) service. This Redis service will be utilized by the instances to cache and share data among themselves. Further information about the Redis settings can be found [here](settings.md#redis).
|
||||
|
||||
!!! 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.0-beta/misc/integrations) folder 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.0-rc1/misc/integrations) folder of the repository for more information.
|
||||
|
||||
Clustered database backends setup are out-of-the-scope of this documentation.
|
||||
|
||||
|
|
@ -817,7 +817,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -877,7 +877,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -904,7 +904,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -1067,7 +1067,7 @@ spec:
|
|||
|
||||
### Namespaces
|
||||
|
||||
Starting from version `1.6.0-beta`, BunkerWeb's autoconf stacks now support namespaces. This feature enables you to manage multiple clusters of BunkerWeb instances and services on the same Kubernetes cluster. To take advantage of namespaces, simply set the `namespace` metadata field on your BunkerWeb instances and services. Here's an example:
|
||||
Starting from version `1.6.0-rc1`, BunkerWeb's autoconf stacks now support namespaces. This feature enables you to manage multiple clusters of BunkerWeb instances and services on the same Kubernetes cluster. To take advantage of namespaces, simply set the `namespace` metadata field on your BunkerWeb instances and services. Here's an example:
|
||||
|
||||
```yaml
|
||||
apiVersion: apps/v1
|
||||
|
|
@ -1104,7 +1104,7 @@ metadata:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: NAMESPACES
|
||||
|
|
@ -1184,7 +1184,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: USE_KUBERNETES_FQDN
|
||||
|
|
@ -1218,7 +1218,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.0-beta/misc/integrations) folder 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.0-rc1/misc/integrations) folder of the repository for more information.
|
||||
|
||||
Clustered database backends setup are out-of-the-scope of this documentation.
|
||||
|
||||
|
|
@ -1232,7 +1232,7 @@ x-bw-env: &bw-env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -1261,7 +1261,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes" # Mandatory label for the autoconf service to identify the BunkerWeb instance
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-env
|
||||
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
|
||||
|
|
@ -1282,7 +1282,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
SWARM_MODE: "yes"
|
||||
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Remember to set a stronger password for the database
|
||||
|
|
@ -1398,7 +1398,7 @@ networks:
|
|||
|
||||
### Namespaces
|
||||
|
||||
Starting from version `1.6.0-beta`, BunkerWeb's Autoconf stacks now support namespaces. This feature enables you to manage multiple "*clusters*" of BunkerWeb instances and services on the same Docker host. To take advantage of namespaces, simply set the `NAMESPACE` label on your services. Here's an example:
|
||||
Starting from version `1.6.0-rc1`, BunkerWeb's Autoconf stacks now support namespaces. This feature enables you to manage multiple "*clusters*" of BunkerWeb instances and services on the same Docker host. To take advantage of namespaces, simply set the `NAMESPACE` label on your services. Here's an example:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
|
|
@ -1429,7 +1429,7 @@ networks:
|
|||
...
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
...
|
||||
deploy:
|
||||
mode: global
|
||||
|
|
@ -1441,7 +1441,7 @@ networks:
|
|||
- "bunkerweb.NAMESPACE=my-namespace" # Set the namespace for the BunkerWeb instance
|
||||
...
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
NAMESPACES: "my-namespace my-other-namespace" # Only listen to these namespaces
|
||||
...
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ The first step is to install the plugin by putting the plugin files inside the c
|
|||
services:
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- ./bw-data:/data
|
||||
...
|
||||
|
|
@ -126,7 +126,7 @@ The first step is to install the plugin by putting the plugin files inside the c
|
|||
services:
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- ./bw-data:/data
|
||||
...
|
||||
|
|
@ -164,7 +164,7 @@ The first step is to install the plugin by putting the plugin files inside the c
|
|||
services:
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- /shared/bw-plugins:/data/plugins
|
||||
...
|
||||
|
|
@ -211,7 +211,7 @@ The first step is to install the plugin by putting the plugin files inside the c
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -251,7 +251,7 @@ The first step is to install the plugin by putting the plugin files inside the c
|
|||
|
||||
!!! 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.0-beta/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.0-rc1/src/common/core) (already included in BunkerWeb but they are plugins, technically speaking).
|
||||
|
||||
What a plugin structure looks like :
|
||||
```
|
||||
|
|
@ -529,7 +529,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.0-beta/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.0-rc1/src/bw/lua/bunkerweb) of the repository.
|
||||
|
||||
### Jobs
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
!!! tip "Going further"
|
||||
|
||||
To demonstrate the use of BunkerWeb, we will deploy a dummy "Hello World" web application as an example. See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/examples) of the repository to get real-world examples.
|
||||
To demonstrate the use of BunkerWeb, we will deploy a dummy "Hello World" web application as an example. See the [examples folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/examples) of the repository to get real-world examples.
|
||||
|
||||
## Protect HTTP applications
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ You will find more settings about reverse proxy in the [settings section](settin
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -46,7 +46,7 @@ You will find more settings about reverse proxy in the [settings section](settin
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-api-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
|
||||
|
|
@ -260,7 +260,7 @@ You will find more settings about reverse proxy in the [settings section](settin
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -273,7 +273,7 @@ You will find more settings about reverse proxy in the [settings section](settin
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-api-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
|
||||
|
|
@ -584,7 +584,7 @@ REAL_IP_HEADER=X-Forwarded-For
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -599,7 +599,7 @@ REAL_IP_HEADER=X-Forwarded-For
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -614,7 +614,7 @@ REAL_IP_HEADER=X-Forwarded-For
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -688,7 +688,7 @@ REAL_IP_HEADER=proxy_protocol
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -704,7 +704,7 @@ REAL_IP_HEADER=proxy_protocol
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -720,7 +720,7 @@ REAL_IP_HEADER=proxy_protocol
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
environment:
|
||||
USE_REAL_IP: "yes"
|
||||
|
|
@ -816,7 +816,7 @@ For complete list of settings regarding `stream` mode, please refer to the [sett
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080" # Keep it if you want to use Let's Encrypt automation
|
||||
- "10000:10000" # app1
|
||||
|
|
@ -831,7 +831,7 @@ For complete list of settings regarding `stream` mode, please refer to the [sett
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- bw-data:/data
|
||||
environment:
|
||||
|
|
@ -882,7 +882,7 @@ For complete list of settings regarding `stream` mode, please refer to the [sett
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080" # Keep it if you want to use Let's Encrypt automation
|
||||
- "10000:10000" # app1
|
||||
|
|
@ -931,7 +931,7 @@ For complete list of settings regarding `stream` mode, please refer to the [sett
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
# Keep it if you want to use Let's Encrypt automation
|
||||
- published: 80
|
||||
|
|
@ -1075,7 +1075,7 @@ Some integrations provide more convenient ways to apply configurations, such as
|
|||
```yaml
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
- |
|
||||
CUSTOM_CONF_SERVER_HTTP_hello-world=
|
||||
|
|
@ -1118,7 +1118,7 @@ Some integrations provide more convenient ways to apply configurations, such as
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- ./bw-data:/data
|
||||
...
|
||||
|
|
@ -1188,7 +1188,7 @@ Some integrations provide more convenient ways to apply configurations, such as
|
|||
|
||||
```yaml
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
volumes:
|
||||
- ./bw-data:/data
|
||||
...
|
||||
|
|
@ -1353,7 +1353,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -1368,7 +1368,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.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-api-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
|
||||
|
|
@ -1462,7 +1462,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
labels:
|
||||
- "bunkerweb.INSTANCE=yes"
|
||||
environment:
|
||||
|
|
@ -1475,7 +1475,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.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
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
|
||||
|
|
@ -1490,7 +1490,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.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -1635,7 +1635,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
volumes:
|
||||
- /shared/www:/var/www/html
|
||||
...
|
||||
|
|
@ -1822,7 +1822,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.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
USE_IPv6: "yes"
|
||||
...
|
||||
|
|
@ -1861,7 +1861,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.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
USE_IPv6: "yes"
|
||||
...
|
||||
|
|
|
|||
|
|
@ -372,7 +372,7 @@ This BunkerWeb plugin acts as a [CrowdSec](https://crowdsec.net/) bouncer. It wi
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080"
|
||||
- "443:8443"
|
||||
|
|
@ -389,7 +389,7 @@ This BunkerWeb plugin acts as a [CrowdSec](https://crowdsec.net/) bouncer. It wi
|
|||
syslog-address: "udp://10.10.10.254:514"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
environment:
|
||||
|
|
@ -839,7 +839,7 @@ You can quickly protect sensitive resources like the admin area for example, by
|
|||
|
||||
### Auth request
|
||||
|
||||
You can deploy complex authentication (e.g. SSO), by using the auth request settings (see [here](https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/) for more information on the feature). Please note that you will find [Authelia](https://www.authelia.com/) and [Authentik](https://goauthentik.io/) examples in the [repository](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/examples).
|
||||
You can deploy complex authentication (e.g. SSO), by using the auth request settings (see [here](https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-subrequest-authentication/) for more information on the feature). Please note that you will find [Authelia](https://www.authelia.com/) and [Authentik](https://goauthentik.io/) examples in the [repository](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/examples).
|
||||
|
||||
**Auth request settings are related to reverse proxy rules.**
|
||||
|
||||
|
|
|
|||
|
|
@ -74,16 +74,16 @@
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
...
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
...
|
||||
```
|
||||
|
||||
|
|
@ -116,7 +116,7 @@
|
|||
Them, you can update BunkerWeb package :
|
||||
|
||||
```shell
|
||||
sudo apt install -y bunkerweb=1.6.0-beta
|
||||
sudo apt install -y bunkerweb=1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading BunkerWeb package when executing `apt upgrade`, you can use the following command :
|
||||
|
|
@ -140,7 +140,7 @@
|
|||
Them, you can update BunkerWeb package :
|
||||
|
||||
```shell
|
||||
sudo dnf install -y bunkerweb-1.6.0-beta
|
||||
sudo dnf install -y bunkerweb-1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading BunkerWeb package when executing `dnf upgrade`, you can use the following command :
|
||||
|
|
@ -460,16 +460,16 @@
|
|||
```yaml
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
...
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
...
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
...
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
...
|
||||
```
|
||||
|
||||
|
|
@ -502,7 +502,7 @@
|
|||
Them, you can update BunkerWeb package :
|
||||
|
||||
```shell
|
||||
sudo apt install -y bunkerweb=1.6.0-beta
|
||||
sudo apt install -y bunkerweb=1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading BunkerWeb package when executing `apt upgrade`, you can use the following command :
|
||||
|
|
@ -526,7 +526,7 @@
|
|||
Them, you can update BunkerWeb package :
|
||||
|
||||
```shell
|
||||
sudo dnf install -y bunkerweb-1.6.0-beta
|
||||
sudo dnf install -y bunkerweb-1.6.0-rc1
|
||||
```
|
||||
|
||||
To prevent upgrading BunkerWeb package when executing `dnf upgrade`, you can use the following command :
|
||||
|
|
@ -758,7 +758,7 @@ We added a **namespace** feature to the autoconf integrations. Namespaces allow
|
|||
|
||||
!!! warning "Read this if you were a 1.4.X user"
|
||||
|
||||
A lot of things changed since the 1.4.X releases. Container-based integrations stacks contain more services but, trust us, fundamental principles of BunkerWeb are still there. You will find ready to use boilerplates for various integrations in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/misc/integrations) folder of the repository.
|
||||
A lot of things changed since the 1.4.X releases. Container-based integrations stacks contain more services but, trust us, fundamental principles of BunkerWeb are still there. You will find ready to use boilerplates for various integrations in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/misc/integrations) folder of the repository.
|
||||
|
||||
### Scheduler
|
||||
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -131,7 +131,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
|
||||
|
|
@ -147,7 +147,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
TOTP_SECRETS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
|
||||
|
|
@ -204,7 +204,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -220,7 +220,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -236,7 +236,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-db
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bw-docker
|
||||
environment:
|
||||
|
|
@ -259,7 +259,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-docker
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
TOTP_SECRETS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
|
||||
|
|
@ -318,7 +318,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -348,7 +348,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -366,7 +366,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- bw-db
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -395,7 +395,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
- "node.role == manager"
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
TOTP_SECRETS: "mysecret" # Remember to set a stronger secret key (see the Prerequisites section)
|
||||
|
|
@ -511,7 +511,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -571,7 +571,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -598,7 +598,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -703,7 +703,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-ui
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -786,7 +786,7 @@ Review your final BunkerWeb UI URL and then click on the `Setup` button. Once th
|
|||
|
||||
## Accessing logs
|
||||
|
||||
Beginning with version `1.6.0-beta`, the method of accessing logs has changed. This update specifically impacts **Docker, Autoconf, and Swarm** Integrations. Logs are now exclusively accessed from the `/var/log/bunkerweb` directory.
|
||||
Beginning with version `1.6.0-rc1`, the method of accessing logs has changed. This update specifically impacts **Docker, Autoconf, and Swarm** Integrations. Logs are now exclusively accessed from the `/var/log/bunkerweb` directory.
|
||||
|
||||
To keep the logs accessible from the web UI, you will need to use `syslog-ng` to forward the logs to a file in the `/var/log/bunkerweb` directory.
|
||||
|
||||
|
|
@ -801,7 +801,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -819,7 +819,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
|
||||
|
|
@ -851,7 +851,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
DATABASE_URI: "mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db" # Remember to set a stronger password for the database
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -922,7 +922,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -941,7 +941,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
|
||||
|
|
@ -961,7 +961,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -980,7 +980,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *bw-ui-env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -1074,7 +1074,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -1109,7 +1109,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -1131,7 +1131,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
syslog-address: "udp://10.20.30.254:514" # This is the syslog-ng container address
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -1166,7 +1166,7 @@ To keep the logs accessible from the web UI, you will need to use `syslog-ng` to
|
|||
- "node.role == manager"
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -1425,7 +1425,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
!!! info "Database backend"
|
||||
|
||||
If you want another Database backend than MariaDB please refer to the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/misc/integrations) of the repository.
|
||||
If you want another Database backend than MariaDB please refer to the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/misc/integrations) of the repository.
|
||||
|
||||
Here is the docker-compose boilerplate that you can use (don't forget to edit the `changeme` data) :
|
||||
|
||||
|
|
@ -1436,7 +1436,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -1448,7 +1448,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
BUNKERWEB_INSTANCES: "bunkerweb" # Make sure to set the correct instance name
|
||||
|
|
@ -1474,7 +1474,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -1537,7 +1537,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
!!! info "Database backend"
|
||||
|
||||
If you want another Database backend than MariaDB please refer to the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/misc/integrations) of the repository.
|
||||
If you want another Database backend than MariaDB please refer to the docker-compose files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/misc/integrations) of the repository.
|
||||
|
||||
Here is the docker-compose boilerplate that you can use (don't forget to edit the `changeme` data) :
|
||||
|
||||
|
|
@ -1549,7 +1549,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- "80:8080/tcp"
|
||||
- "443:8443/tcp"
|
||||
|
|
@ -1564,7 +1564,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -1578,7 +1578,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-db
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bw-docker
|
||||
environment:
|
||||
|
|
@ -1612,7 +1612,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -1675,7 +1675,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
!!! info "Database backend"
|
||||
|
||||
If you want another Database backend than MariaDB please refer to the stack files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/misc/integrations) of the repository.
|
||||
If you want another Database backend than MariaDB please refer to the stack files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/misc/integrations) of the repository.
|
||||
|
||||
Here is the stack boilerplate that you can use (don't forget to edit the `changeme` data) :
|
||||
|
||||
|
|
@ -1687,7 +1687,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -1716,7 +1716,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -1732,7 +1732,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-db
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -1777,7 +1777,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
- bw-universe
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *ui-env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
@ -1837,7 +1837,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
|
||||
!!! info "Database backend"
|
||||
|
||||
If you want another Database backend than MariaDB please refer to the yaml files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-beta/misc/integrations) of the repository.
|
||||
If you want another Database backend than MariaDB please refer to the yaml files in the [misc/integrations folder](https://github.com/bunkerity/bunkerweb/tree/v1.6.0-rc1/misc/integrations) of the repository.
|
||||
|
||||
Here is the yaml boilerplate that you can use (don't forget to edit the `changeme` data) :
|
||||
|
||||
|
|
@ -1894,7 +1894,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -1954,7 +1954,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -1981,7 +1981,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -2084,7 +2084,7 @@ After a successful login/password combination, you will be prompted to enter you
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-ui
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -47,7 +47,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
networks:
|
||||
- bw-universe
|
||||
- bw-db
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -47,7 +47,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
networks:
|
||||
- bw-universe
|
||||
- bw-db
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -47,7 +47,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
networks:
|
||||
- bw-universe
|
||||
- bw-db
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -18,7 +18,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
- bw-docker
|
||||
|
|
@ -31,7 +31,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -17,7 +17,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -44,7 +44,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -17,7 +17,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -17,7 +17,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -44,7 +44,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -17,7 +17,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -16,7 +16,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- bw-db
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -17,7 +17,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- 80:8080
|
||||
- 443:8443
|
||||
|
|
@ -16,7 +16,7 @@ services:
|
|||
- bw-services
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
depends_on:
|
||||
- bunkerweb
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -109,7 +109,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -136,7 +136,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -238,7 +238,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-ui
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -120,7 +120,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -147,7 +147,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -109,7 +109,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -136,7 +136,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -238,7 +238,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-ui
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -120,7 +120,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -147,7 +147,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -109,7 +109,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -136,7 +136,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -238,7 +238,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-ui
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ spec:
|
|||
containers:
|
||||
# using bunkerweb as name is mandatory
|
||||
- name: bunkerweb
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
securityContext:
|
||||
runAsUser: 101
|
||||
|
|
@ -120,7 +120,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-controller
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
@ -147,7 +147,7 @@ spec:
|
|||
serviceAccountName: sa-bunkerweb
|
||||
containers:
|
||||
- name: bunkerweb-scheduler
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
imagePullPolicy: Always
|
||||
env:
|
||||
- name: KUBERNETES_MODE
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -61,7 +61,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -61,7 +61,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
@ -61,7 +61,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-ui:
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-ui:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
ADMIN_USERNAME: "changeme"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-env: &env
|
|||
|
||||
services:
|
||||
bunkerweb:
|
||||
image: bunkerity/bunkerweb:1.6.0-beta
|
||||
image: bunkerity/bunkerweb:1.6.0-rc1
|
||||
ports:
|
||||
- published: 80
|
||||
target: 8080
|
||||
|
|
@ -29,7 +29,7 @@ services:
|
|||
- "bunkerweb.INSTANCE=yes"
|
||||
|
||||
bw-autoconf:
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-autoconf:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
DOCKER_HOST: "tcp://bw-docker:2375"
|
||||
|
|
@ -43,7 +43,7 @@ services:
|
|||
- "node.role == worker"
|
||||
|
||||
bw-scheduler:
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-beta
|
||||
image: bunkerity/bunkerweb-scheduler:1.6.0-rc1
|
||||
environment:
|
||||
<<: *env
|
||||
BUNKERWEB_INSTANCES: ""
|
||||
|
|
|
|||
0
misc/update-version.sh
Normal file → Executable file
0
misc/update-version.sh
Normal file → Executable file
|
|
@ -1,7 +1,7 @@
|
|||
[project]
|
||||
name = "BunkerWeb"
|
||||
description = "Make your web services secure by default !"
|
||||
version = "1.6.0-beta"
|
||||
version = "1.6.0-rc1"
|
||||
authors = [
|
||||
{ name = "Bunkerity", email = "contact@bunkerity.com" }
|
||||
]
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1.6.0-beta
|
||||
1.6.0-rc1
|
||||
|
|
@ -67,7 +67,7 @@ RUN cp helpers/bwcli /usr/bin/ && \
|
|||
chmod 660 INTEGRATION
|
||||
|
||||
LABEL maintainer="Bunkerity <contact@bunkerity.com>"
|
||||
LABEL version="1.6.0-beta"
|
||||
LABEL version="1.6.0-rc1"
|
||||
LABEL url="https://www.bunkerweb.io"
|
||||
LABEL bunkerweb.type="autoconf"
|
||||
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ RUN cp helpers/bwcli /usr/bin/ && \
|
|||
ln -s /proc/1/fd/1 /var/log/bunkerweb/access.log
|
||||
|
||||
LABEL maintainer="Bunkerity <contact@bunkerity.com>"
|
||||
LABEL version="1.6.0-beta"
|
||||
LABEL version="1.6.0-rc1"
|
||||
LABEL url="https://www.bunkerweb.io"
|
||||
LABEL bunkerweb.type="bunkerweb"
|
||||
LABEL bunkerweb.INSTANCE="bunkerweb"
|
||||
|
|
|
|||
Loading…
Reference in a new issue