public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-26 08:01:47 +00:00
Code Issues Releases Wiki Activity

Add Prowlarr. Grrowwwlllll!

Browse Source
This commit is contained in:
David Young
2021-10-27 19:19:22 +13:00
committed by GitHub
parent ffa4314919
commit 7388b7b504
20 changed files with 125 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
manuscript/ha-docker-swarm/shared-storage-gluster.md
View File

@@ -165,7 +165,7 @@ After completing the above, you should have:
* [X] Resiliency in the event of the failure of a single (gluster) node
[^1]: Future enhancements to this recipe include:
1. Migration of shared storage from GlusterFS to Ceph ()[#2](https://gitlab.funkypenguin.co.nz/funkypenguin/geeks-cookbook/issues/2))
2. Correct the fact that volumes don't automount on boot ([#3](https://gitlab.funkypenguin.co.nz/funkypenguin/geeks-cookbook/issues/3))
1. Migration of shared storage from GlusterFS to Ceph
2. Correct the fact that volumes don't automount on boot
--8<-- "recipe-footer.md"

2
manuscript/ha-docker-swarm/traefik-forward-auth/index.md
View File

@@ -19,7 +19,7 @@ This is the role of Traefik Forward Auth.
When employing Traefik Forward Auth as "[middleware](https://doc.traefik.io/traefik/middlewares/forwardauth/)", the forward-auth process sits in the middle of this transaction - traefik receives the incoming request, "checks in" with the auth server to determine whether or not further authentication is required. If the user is authenticated, the auth server returns a 200 response code, and Traefik is authorized to forward the request to the backend. If not, traefik passes the auth server response back to the user - this process will usually direct the user to an authentication provider (_GitHub, Google, etc_), so that they can perform a login.
Illustrated below:
![Traefik Forward Auth](../images/traefik-forward-auth.png)
![Traefik Forward Auth](../../images/traefik-forward-auth.png)
The advantage under this design is additional security. If I'm deploying a web app which I expect only an authenticated user to require access to (*unlike something intended to be accessed publically, like [Linx](/recipes/linx/)*), I'll pass the request through Traefik Forward Auth. The overhead is negligible, and the additional layer of security is well-worth it.