Improve page experience using try_files-ish approach for SPA/static pages

[inFocus7]

Description

Motivation

A minor annoyance I hit is during development (and maybe it happens in production setups), I try to reload /deployed, but this ends up loading a next.js directory tree instead of the page. We should be serving the page itself.

Changes

• Instead of serving the paths directly (which leads to /deployed -> display directory), we now serve static files and html (if found).
  • Using the try_files approach like in nginx, we fallback from (1) exact file matches, (2) *.html, (3) root SPA.
  • Note: For the final fallback, had to use ServeContent as dictated in the go docs, since hitting / redirects to , which i believe redirect to `/`, back to , infinitely.

  • As another special case, ServeFile redirects any request where r.URL.Path ends in "/index.html" to the same path, without the final "index.html". To avoid such redirects either modify the path or use ServeContent.

Change Type

/kind fix

Changelog

Fixes static page UI loading, allowing load of non-root paths.

Additional Notes

Validation

Simply ran make run-docker. May require browser cache clearance.

Before

static.serve.-.before.mp4

After

static.serve.-.after.mp4

[Copilot]

Pull request overview

Adjusts the embedded UI static file serving logic to behave more like try_files, improving reload behavior for Next.js static export routes (e.g., /deployed).

Changes:

• Replaces the plain http.FileServer UI handler with a custom resolver: exact file → <path>.html → index.html.
• Uses http.ServeContent for the index.html fallback to avoid FileServer redirect behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.