Route eln.ddomlab.org:5000 to eln_server, keeping /pth on PTH

[rcb1409]

Why

On the old server, eln.ddomlab.org:5000 was eln_server, the scanner page, label printing and the autofill/peroxide API, which also mounted the PTH routes under /pth. Since the cutover this block sends everything to the pth container, so everything except /pth/... returns 404. That includes the scanner page and the eln-autofill timer, which has failed every 10 minutes since Sep 22.

eln_server now runs as its own container, eln-server on lab-net (ddomlab/eln_server#3).

Change

eln.ddomlab.org:5000 {
	@pth path /pth /pth/*
	handle @pth { reverse_proxy pth:5000 }        # sensor + MEDUSA
	handle      { reverse_proxy eln-server:5000 } # everything else
	log { output file /var/log/caddy/eln-5000-access.log { ... } }
}

This address also gets a request log, with the same rotation as the main site (/var/log/caddy/eln-5000-access.log), so scanner-page use can be checked later.

Tested

• caddy adapt: the syntax is valid.
• Routing: I ran Caddy locally with this exact block in front of stand-in pth and eln-server containers:

Request	Went to
GET /pth/api/ndays?days=1, /pth/dashboard, /pth	pth
GET /pthology	eln-server (a prefix lookalike doesn't match)
GET /, /ping, /add_resource_interface, POST /api/autofill	eln-server

Deploy order

Start the eln-server container first, then git pull && sudo docker compose restart caddy in /opt/edge. Until the container exists, non-/pth requests would get 502 instead of today's 404; /pth isn't affected either way.

🤖 Generated with Claude Code