| Age | Commit message (Collapse) | Author |
|---|
|
- Spelling: usefull→useful, alread→already, sessiont→session, propper→proper,
standarn→standard (file rename), Developmers→Developers, figjit→fig,
dnmcli→nmcli
- Grammar: every aliases→alias, it's→its (possessive), main objectives→objective,
necessary for accomplish→to accomplish, follow to it as of→follow it as if,
Advances come only of you→if you, Defeat is finally give up→giving up,
Where are humans there is→Where there are humans, there is, spent→spend,
It's not too be→to be, If you they/Of you try→If you try
- Phrasing: hook off→knock off, Meditation must nothing be fancy→need not be fancy,
we will also setting up→set up, showcases hows→showcases how
- Career guide: Safe→Save, kudos'→kudos, automate all away→automate it all away
- About: hey→they, simplify English/German titles in novels
- F3s: VNC address f0→f2 for third VM, zrepl encrypted doc clarification
- Rename: standarn-ml.gmi→standard-ml.gmi with index link updates
Co-authored-by: Cursor <cursoragent@cursor.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
content-gemtext
|
|
|
|
Removed the LAN ingress update notice from Part 8 entirely, as the LAN
ingress content has been moved to Part 7 where ingresses were originally
introduced.
|
|
Relocated the "Exposing services via LAN ingress" section from Part 8
(Observability) to Part 7 (k3s and first pod deployments), as Part 7 is
where ingresses were originally introduced. Updated the Part 8 update
notice to reference Part 7 for LAN ingress implementation details.
|
|
Removed the detailed CARP failover testing section including
failover/failback test commands and results. The section was too
detailed for the blog post scope.
|
|
Updated client-side setup section to include DNS configuration.
Added instructions for adding /etc/hosts entries pointing LAN
service domains to the CARP VIP (192.168.1.138).
Renamed section from 'Client-side CA trust' to 'Client-side DNS
and CA setup' to reflect both DNS and certificate configuration.
|
|
Keep only Linux/FreeBSD setup instructions that match the actual
infrastructure. Removed unnecessary platform-specific instructions
for macOS and Windows from the Client-side CA trust section.
|
|
Gemini gemtext only supports headers up to ###. Changed all ####
headers to the *Header*: format for proper Gemini compatibility.
|
|
Added update notice at the beginning of the blog post to inform
readers about the LAN ingress feature addition in February 2026.
The notice references the new section and summarizes key features.
|
|
- Document CARP + relayd architecture for LAN access
- Explain cert-manager setup with self-signed CA
- Provide example LAN ingress configuration for Grafana
- Include CARP failover testing results
- Document three TLS offloaders (OpenBSD, Traefik, stunnel)
- Show step-by-step setup for FreeBSD relayd
- Add client-side CA trust instructions for Linux/macOS/Windows
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019c086d-c760-779d-b740-0f748094b62a
Co-authored-by: Amp <amp@ampcode.com>
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019c086d-c760-779d-b740-0f748094b62a
Co-authored-by: Amp <amp@ampcode.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Updated all `wg show` output examples to include IPv6 addresses
in the "allowed ips" field for mesh peers.
Changes:
- All mesh peers now show dual-stack: 192.168.2.X/32, fd42:beef:cafe:2::X/128
- Roaming client output updated to show single gateway peer
- Reflects actual dual-stack WireGuard configuration
This makes the example outputs consistent with the IPv6 implementation
documented earlier in the blog post.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
