lantern-external-services

Configuration node for Lantern's /api/external/<short>/* reverse proxy.

Lantern reads the Services YAML fence below at request time (with a short TTL cache) and forwards browser calls to the named upstream. Adding a new upstream service is a single YAML edit — no Lantern code changes needed.

Services

services:
  sprout-engine:
    base: http://sprout-engine:9295

How it works

A browser-side component (e.g. <wanderland-button service="sprout-engine">) addresses the upstream as:

Lantern's proxy strips the /api/external/sprout-engine prefix and forwards the remainder to http://localhost:9295/api/engine/inspect/route/refresh, preserving method, query string, body, and a small allowlist of headers (Content-Type, X-Wanderland-Trace, X-Oculus-Session). The response status, content-type, and body are streamed back unchanged.

This keeps CORS off the table (the browser only ever talks to Lantern) and keeps service addressing out of the page markup.