Personal Catalogue: React, Express & MongoDB — Chapter 10, Exercise 2
=====================================================================

TASK
Configure the nginx location /catalogue/ block against a real running
instance of the app (a second local nginx config is fine for testing),
and confirm both a page load and a real API request succeed through
the proxy, with Express's own server.js completely unchanged from
Chapter 9.

SOLUTION

Backend running exactly as Chapter 9 left it, with the Chapter 10
frontend build in place:

  cd catalogue-api
  node server.js
  # listening on port 4000, serving both /api/items and the
  # /catalogue-prefixed static build, completely unmodified from Ch.9

A minimal local nginx config for testing (e.g. /etc/nginx/sites-available/test-catalogue):

  server {
      listen 8080;
      server_name localhost;

      location /catalogue/ {
          proxy_pass http://localhost:4000/;
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;
      }
  }

  sudo ln -s /etc/nginx/sites-available/test-catalogue /etc/nginx/sites-enabled/
  sudo nginx -t
  sudo systemctl reload nginx

Testing a page load through the proxy:

  curl -i http://localhost:8080/catalogue/

Output: a real 200 response containing the built index.html, with its
own <script>/<link> tags correctly referencing /catalogue/assets/...
paths (from Exercise 1), served indirectly through nginx rather than
hitting port 4000 directly.

Testing a real API request through the proxy:

  curl -i http://localhost:8080/catalogue/api/items

Output: a real 200 response with the actual JSON items array -- proving
nginx correctly stripped /catalogue from the incoming request path
before forwarding to Express, which received a plain, familiar request
for /api/items and handled it with the exact same route Chapter 3
wrote, completely unaware anything about its own URL prefix had
changed.

Confirming server.js needed no edits: a diff between this chapter's
server.js and Chapter 9's own version shows zero differences -- every
fix in this chapter lived entirely in vite.config.js, .env.production,
and the nginx config, never in the Express application itself.

WHY THIS WORKS AS AN ANSWER
----------------------------
It stands up a real, working nginx reverse proxy against the actual
running app, verifies both a page load and a genuine API call succeed
through it with real HTTP responses, and explicitly confirms the claim
that Express's own code needed no changes at all -- checked directly
against Chapter 9's own file rather than merely asserted.