chore(preccomit): run precocmit (#13387)
**Description** <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> ⚒️ Fixes # <!--(issue)--> **⚙️ Type of change** - [ ] ⚙️ Feature/App addition - [ ] 🪛 Bugfix - [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 🔃 Refactor of current code **🧪 How Has This Been Tested?** <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration --> **📃 Notes:** <!-- Please enter any other relevant information here --> **✔️ Checklist:** - [ ] ⚖️ My code follows the style guidelines of this project - [ ] 👀 I have performed a self-review of my own code - [ ] #️⃣ I have commented my code, particularly in hard-to-understand areas - [ ] 📄 I have made corresponding changes to the documentation - [ ] ⚠️ My changes generate no new warnings - [ ] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [ ] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
This commit is contained in:
@@ -103,6 +103,7 @@ The last step is adding the `forwardauth` along with the standard `ingress` sett
|
||||
- In this example we use the same name as above, or `auth`. Click `Add` to the `Traefik Middlewares` section, and enter your `forwardauth` name.
|
||||
|
||||

|
||||
|
||||
### References
|
||||
|
||||
The origin material for this guide is available on the [LLDAP Github](https://github.com/lldap/lldap). While further information on Authelia can be found on their [Github](https://github.com/authelia/authelia) and [website](https://www.authelia.com/).
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
# Blocky Setup Guide
|
||||
|
||||
This will guide you through the basic setup of Blocky which is the preferred DNS solution for TrueCharts. This guide will cover basic setup options which will get you up and running and is not all inclusive. Configuring your devices to use Blocky is out of scope of this guide.
|
||||
This will guide you through the basic setup of Blocky which is the preferred DNS solution for TrueCharts. This guide will cover basic setup options which will get you up and running and is not all inclusive. Configuring your devices to use Blocky is out of scope of this guide.
|
||||
|
||||
## Upstream DNS
|
||||
|
||||
Blocky has the following DNS entries configured by default. They can be overridden to your personal preferences or left as default. Here are some common ones:
|
||||
Blocky has the following DNS entries configured by default. They can be overridden to your personal preferences or left as default. Here are some common ones:
|
||||
|
||||
- 1.1.1.1
|
||||
- 1.0.0.1
|
||||
@@ -23,13 +23,13 @@ Blocky has the following DNS entries configured by default. They can be overrid
|
||||
- 76.76.2.0
|
||||
- 76.76.10.0
|
||||
|
||||
Blocky supports 3 methods for upstream DNS. You can use any combination of the below.
|
||||
Blocky supports 3 methods for upstream DNS. You can use any combination of the below.
|
||||
|
||||
- UDP - Basic DNS
|
||||
- DoT - DNS over TLS
|
||||
- DoH - DNS over HTTPS
|
||||
|
||||
While UDP provides no security for DNS both DoT and DoH will encrypt DNS request. DoH has the added benefit of privacy since DNS traffic will appear as HTTPS traffic.
|
||||
While UDP provides no security for DNS both DoT and DoH will encrypt DNS request. DoH has the added benefit of privacy since DNS traffic will appear as HTTPS traffic.
|
||||
|
||||
### UDP DNS Setup
|
||||
|
||||
@@ -83,10 +83,10 @@ certain blocklists if you find legitimate traffic being blocked.
|
||||
|
||||
## Networking
|
||||
|
||||
If you want to use Blocky on your local network to take advantage of the filtering above, or the k8s-gateway below, you
|
||||
If you want to use Blocky on your local network to take advantage of the filtering above, or the k8s-gateway below, you
|
||||
need to setup a static ip address and leave the default setting DNS TCP Service and DNS UDP Service as LoadBalancer.
|
||||
|
||||
You need to configure the devices on your network to use the static IP address configured above. This can be done per device or by changing the DHCP or DNS settings on your router.
|
||||
You need to configure the devices on your network to use the static IP address configured above. This can be done per device or by changing the DHCP or DNS settings on your router.
|
||||
|
||||
## k8s-Gateway Configuration
|
||||
|
||||
|
||||
@@ -14,7 +14,6 @@ It is important to configure Scale with reliable nameserver to avoid issues hand
|
||||
|
||||

|
||||
|
||||
|
||||
## Install clusterissuer App
|
||||
|
||||
:::note
|
||||
@@ -37,7 +36,7 @@ Login to Cloudflare dashboard and go to the [Cloudflare API Tokens](https://dash
|
||||
|
||||

|
||||
|
||||
The recommended `API Token` permissions are below:
|
||||
The recommended `API Token` permissions are below:
|
||||

|
||||
|
||||
#### Cloudflare ACME Issuer Settings
|
||||
|
||||
@@ -27,7 +27,7 @@ Our customized version of MetalLB is only intended for use with other TrueCharts
|
||||
Install `metallb` from `operators` train first. There is no config, so just hit save.
|
||||
|
||||
If you encounter an error upon install, run the following command as root from system settings -> shell and attempt the install again:
|
||||
```k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete```
|
||||
`k3s kubectl delete --grace-period 30 --v=4 -k https://github.com/truecharts/manifests/delete`
|
||||
|
||||
If you previously had `metallb` installed and encounter an error, delete the old version, then run the above command before proceeding to install the `metallb` operator.
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ service:
|
||||
main:
|
||||
enabled: false
|
||||
port: 9999
|
||||
|
||||
|
||||
operator:
|
||||
verify:
|
||||
enabled: true
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
# Authelia + LLDAP + Traefik ForwardAuth Setup guide
|
||||
|
||||
Please refer to the full [Authelia + LLDAP + Traefik ForwardAuth Setup guide](https://truecharts.org/charts/enterprise/authelia/Setup-Guide) for a quick guide should take you through the steps necessary to setup `Authelia` as your `forwardAuth` for `Traefik`.
|
||||
Please refer to the full [Authelia + LLDAP + Traefik ForwardAuth Setup guide](https://truecharts.org/charts/enterprise/authelia/Setup-Guide) for a quick guide should take you through the steps necessary to setup `Authelia` as your `forwardAuth` for `Traefik`.
|
||||
|
||||
@@ -126,7 +126,7 @@ vaultwarden:
|
||||
push:
|
||||
enabled: false
|
||||
# installationId:
|
||||
# installationKey:
|
||||
# installationKey:
|
||||
|
||||
## Logging options. https://github.com/dani-garcia/bitwarden_rs/wiki/Logging
|
||||
log:
|
||||
|
||||
Reference in New Issue
Block a user