jdsjkdjk
Some checks failed
Build and Deploy / changes (push) Successful in 1s
Build and Deploy / deploy (push) Successful in 6s
Build and Deploy / deploy-lean (push) Has been cancelled

This commit is contained in:
2026-10-19 22:28:12 +02:00
parent 0f7c765d61
commit 097160a6cd
7 changed files with 92 additions and 25 deletions

View File

@@ -43,7 +43,11 @@ Frontend API URL comes from `NUXT_PUBLIC_API_BASE`
(default `http://localhost:5000`, read via `runtimeConfig.public.apiBase`). The Lean
editor's address comes from `NUXT_PUBLIC_LEAN_URL` (default `http://localhost:8080`,
read via `runtimeConfig.public.leanUrl`) — on an HTTPS site it must be an https://
address too, or the browser blocks it (and the `wss://` derived from it) as mixed content (see `lean/README.md`). The frontend image
address too, or the browser blocks it (and the `wss://` derived from it) as mixed content (see `lean/README.md`). Production
passes `https://mathew.aranroig.com/api/lean`: nginx strips the `/api/lean` prefix and
proxies the rest to `lean:8080`, so the editor's websocket rides the site's own origin
instead of a public port 8080 (the compose service binds that port to the host's
loopback, for dev only). The frontend image
builds it empty: the browser then calls `/api` on its own origin, which nginx routes to
`backend:5000`, while the Nuxt server's own (SSR) `/api` calls go through a `routeRules` proxy
aimed at `NUXT_API_PROXY_TARGET` (`https://mathew.aranroig.com` baked in at image build — the
@@ -447,7 +451,10 @@ copy + an `APP_LANGUAGES` entry + the code in the backend's `SUPPORTED_LOCALES`.
puts `#check` output; there is no `$/lean/plainMessages` anymore). Dev runs the server
with `./dev.sh` (via docker compose; or lean4web natively: `NO_BWRAP=true PORT=8080 npm run prod`).
On an HTTPS site the address must be https (its `wss://` is derived from it — an `http://`
Lean server refuses an https wiki outright).
Lean server refuses an https wiki outright). Production uses
`https://mathew.aranroig.com/api/lean`, which `nginx.conf` proxies to `lean:8080`; the
bundled classic lean4web client still assumes it is served from a root, so behind
`/api/lean` the status bar's link opens a page whose assets 404.
A tool page like this is wired in step: `ToolPage`/`TOOL_PAGE_PATHS`
(`utils/routes.ts`), the page file, `TOOL_LABEL_KEYS`, the `ToolPane` branch and spine
glyph, the sidebar link, and the `PAGE_TOOLS` entry.