gitea: ROOT_URL -> https://gitea.wingard.pro

Second step of the HTTPS front, deliberately its own generation: pointing
ROOT_URL at an HTTPS name that served nothing would have broken the UI's
absolute links. The vhost (40ae3e00) is proven — ACME issued over HTTP-01 and
https://gitea.wingard.pro/ serves 200 with a chain that validates against the
system trust store, so it is a real Let's Encrypt cert rather than self-signed.

Measured before flipping: Gitea already answers the registry Bearer realm on
https, because it derives the scheme from X-Forwarded-Proto. So Docker's auth
flow was already fully TLS and this flip is for the web UI's own links, so
browsing over https stops emitting http URLs.

DOMAIN stays 10.0.1.49: it only affects newly copied SSH clone URLs, and
existing remotes should not churn.

This commit is contained in:

Harley

2026-09-27 16:04:14 -04:00

parent 40ae3e0026

commit 03ded14b9f

1 changed files with 1 additions and 1 deletions

									
										configuration.nix
									
		+1
		-1
	
												View File
												
				@@ -1630,7 +1630,7 @@ PYEOF

				    settings = {

				      server = {

				        DOMAIN = "10.0.1.49";

				        ROOT_URL = "http://10.0.1.49:3010";

				        ROOT_URL = "https://gitea.wingard.pro";

				        HTTP_PORT = 3010;

				        SSH_PORT = 222;

				        DISABLE_SSH = false;