pierrot/home-lab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add sketch of Docker networks with Cloudflare setup

Browse Source
This commit is contained in:
Pierre Vandermeersch
2026-09-10 22:48:23 +02:00
parent 8f4ffe22da
commit 013cdc2746
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
networking/notes.md
+12
View File
@@ -16,3 +16,15 @@ Some notions to check out:
[] pfSense router
[] SSL certs? (certbot)
[] SSH
> 10/9/2026
After some research and to the best of my understanding, a good secure (free) setup for our Docker containers to run would need the following Docker networks:
* `edge` to host 2 containers : `cloudflared` and a reverse proxy (most likely nginx but still needs research).
* `frontend`: this network would host the reverse proxy as well and all other frontend components e.g. `gitea`, portfolio, blog, etc.
* `backend`: hosts backend components e.g. `gitea-db` and the related `gitea`.
The reason I decided to separate `cloudflared` from the frontend is that it could get compromised. In that case, I don't want all my frontend components to be potentially exposed and the reverse proxy to be bypassed.
The setup involves another component here that may be the only one that will not be hosted locally that is Cloudflare. Since Cloudflare allows some neat features for free like caching, DDoS absorption, WAF in conjunction with the tunnel through `cloudflared` (0 port forwarding needed), handling all SSL leaving just clean inbound HTTP traffic reducing latency and overhead on our system.