From 1a4abfc7f2910caf27a9e8d4de88473df824d0c1 Mon Sep 17 00:00:00 2001 From: DavidHerran Date: Tue, 5 May 2026 13:17:34 -0500 Subject: [PATCH] =?UTF-8?q?nginx:=20include=20lethepowerflux.com=20?= =?UTF-8?q?=E2=86=92=20rf-flux.com=20301=20redirect?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The VPS already had a server block redirecting lethepowerflux.com and www.lethepowerflux.com to https://www.rf-flux.com, but it lived only on the live config — not in git. That's why the latest pull complained about local changes that would be overwritten. Adding it here so the repo is the single source of truth for the Nginx config again. Behaviour is unchanged on the VPS (redirect was already in place) — this commit just lets future git pulls flow without manual intervention. --- nginx/conf.d/flux.conf | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/nginx/conf.d/flux.conf b/nginx/conf.d/flux.conf index 31c5707..ab81558 100644 --- a/nginx/conf.d/flux.conf +++ b/nginx/conf.d/flux.conf @@ -6,6 +6,15 @@ upstream nextjs { keepalive 32; } +# Legacy domain redirect — anyone landing on lethepowerflux.com lands on +# the canonical https://www.rf-flux.com host instead. SEO-safe 301. +server { + listen 80; + server_name lethepowerflux.com www.lethepowerflux.com; + + return 301 https://www.rf-flux.com$request_uri; +} + server { listen 80; server_name rf-flux.com www.rf-flux.com;