Initial commit
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
# Caddy Reverse Proxy – Home Server Implementation
|
||||
|
||||
This page is my reference for how I use Caddy as a reverse proxy on the home server.
|
||||
|
||||
For generic concepts, see:
|
||||
|
||||
- [Network / Reverse Proxy](../../../Network/ReverseProxy.md) (when written)
|
||||
- [Security / Certificates](../../../Security/Certificates.md)
|
||||
|
||||
## Scope
|
||||
|
||||
- Caddy virtual hosts for `.lan` domains.
|
||||
- TLS with the internal CA (`tls internal`).
|
||||
- How I add a new internal HTTPS service.
|
||||
|
||||
## Notes / TODO
|
||||
|
||||
- Document the Caddyfile pattern I use for HTTP → HTTPS.
|
||||
- Add a checklist for adding a new service (DNS + Caddy + Docker + Caddy).
|
||||
@@ -0,0 +1,19 @@
|
||||
# dnsmasq – Home Server Implementation
|
||||
|
||||
This page is my reference for how I configured dnsmasq as internal DNS on the home server.
|
||||
|
||||
For generic DNS concepts, see:
|
||||
|
||||
- [Network / DNS](../../../Network/DNS.md)
|
||||
|
||||
## Scope
|
||||
|
||||
- dnsmasq config for `.lan` internal domains.
|
||||
- How clients use the home server as DNS.
|
||||
- How this integrates with Caddy and WireGuard.
|
||||
|
||||
## Notes / TODO
|
||||
|
||||
- Add example dnsmasq config for `vaultwarden.lan`, `home.lan`, etc.
|
||||
- Document how I point LAN clients and VPN clients to this DNS.
|
||||
- Add a short troubleshooting section (cache, logs, typical mistakes).
|
||||
@@ -0,0 +1,15 @@
|
||||
# Monitoring and Dashboard
|
||||
|
||||
This page is my overview of the monitoring stack on the home server.
|
||||
|
||||
## Scope
|
||||
|
||||
- Homepage, Uptime Kuma, Dozzle, Glances.
|
||||
- How they are wired together (ports, Caddy, DNS, Docker).
|
||||
- What I check first when something looks wrong.
|
||||
|
||||
## Notes / TODO
|
||||
|
||||
- Summarise the docker-compose layout for `/srv/ssd/stacks/monitoring`.
|
||||
- Add examples of Homepage widgets and Kuma checks I use.
|
||||
- Document a basic "health check" routine for the server.
|
||||
@@ -0,0 +1,24 @@
|
||||
# WireGuard VPN – Home Server Implementation
|
||||
|
||||
This page is my reference for how I use WireGuard for remote access to the home server.
|
||||
|
||||
For generic concepts, see:
|
||||
|
||||
- [Network / VPN Basics](../../../Network/VPN/Basics.md)
|
||||
- [Security / Certificates](../../../Security/Certificates.md)
|
||||
|
||||
For the original full step-by-step guide I used at the beginning, see:
|
||||
|
||||
- WireGuard v1 doc (legacy) – to be migrated here.
|
||||
|
||||
## Scope
|
||||
|
||||
- IP plans for LAN and VPN.
|
||||
- Server and client roles.
|
||||
- How I add a new peer safely.
|
||||
|
||||
## Notes / TODO
|
||||
|
||||
- Summarise the `wg0.conf` structure from the v1 doc.
|
||||
- Document the exact steps I follow to add a new client.
|
||||
- Add a short troubleshooting section (common mistakes).
|
||||
Reference in New Issue
Block a user