Redirect

[DylanPMunyard]

@claude can your update the config for the haproxy deployment so that 1942.munyard.dev is redirected to bfstats.io

The paths are exactly the same. Bfstats.io is the domain to replace 1942.munyard.dev so the paths are exactly the same. E.g. 1942.munyard.dev/players redirects to bfstats.io/players, 1942.munyard.dev/servers/bf42 redirects to bfstats.io/servers/bf42

[DylanMunyardSixPivot]

@claude can your update the config for the haproxy deployment so that 1942.munyard.dev is redirected to bfstats.io

The paths are exactly the same. Bfstats.io is the domain to replace 1942.munyard.dev so the paths are exactly the same. E.g. 1942.munyard.dev/players redirects to bfstats.io/players, 1942.munyard.dev/servers/bf42 redirects to bfstats.io/servers/bf42

[github-actions]

Claude finished @DylanMunyardSixPivot's task —— View job • claude/issue-1-20250820-1119 • Create PR ➔

---

HAProxy Redirect Configuration ✅

I've successfully configured HAProxy to redirect 1942.munyard.dev to bfstats.io with the same paths.

Todo List

• Read repository setup instructions (CLAUDE.md)
• Find HAProxy configuration files
• Analyze current configuration structure
• Implement redirect rules for 1942.munyard.dev → bfstats.io
• Commit and push changes
• Provide PR creation link

Changes Made

I updated the HAProxy configuration in k3s/haproxy/config.yaml:72 to add a 301 redirect rule:

# Redirect 1942.munyard.dev to bfstats.io with same path
http-request redirect scheme https code 301 location https://bfstats.io%[capture.req.uri] if host_1942

This configuration will:

• Redirect all requests from 1942.munyard.dev to bfstats.io
• Preserve the exact same path (e.g., /players → /players, /servers/bf42 → /servers/bf42)
• Use HTTP 301 (permanent redirect) status code
• Remove the old backend routing rules for 1942.munyard.dev since traffic will be redirected