Portal 2.0: rebuild on React and TypeScript, served entirely through the PSF-HTTP API

.claude/launch.json

@@ -0,0 +1,11 @@
+{
+  "version": "0.0.1",
+  "configurations": [
+    {
+      "name": "psfportal-vite",
+      "runtimeExecutable": "npm",
+      "runtimeArgs": ["run", "dev-client"],
+      "port": 5173
+    }
+  ]
+}

.dockerignore

@@ -0,0 +1,7 @@
+# node_modules must be installed inside the image so bcrypt's native binary
+# matches the container platform, not copied from the (possibly Windows) host.
+node_modules
+public
+.git
+.env
+*.log

.gitignore

@@ -1,8 +1,31 @@
 .DS_Store
 .env
 node_modules
-public/bundle.*
+
+# `public/` is now entirely Vite build output (sources live in src/, static/ and index.html)
+public/
+
 package-lock.json
 yarn.lock
 *swp
 *swo
+
+# ---------------------------------------------------------------------------
+# Client-derived assets. NEVER commit anything in these paths.
+#
+# They are generated from a local PlanetSide client install (see
+# `npm run build-client-assets`) and contain material owned by Daybreak Game
+# Company: item names and description prose from the client's string table, and
+# inventory artwork from its texture archives. The generator is part of this
+# repo; its output is not, and must not be redistributed here or in any image
+# published from here. The app degrades to internal object names and plain grid
+# tiles when these are absent, so a fresh clone still builds and runs.
+# ---------------------------------------------------------------------------
+# `data/*` rather than `data/`: git cannot re-include a file whose parent DIRECTORY is
+# excluded, so the negation below only works against a contents glob.
+data/*
+# ...except the item table, which is committed. Its description prose -- the one clearly
+# copyrightable part -- is stripped before commit; what remains is names, types and grid
+# footprints, the factual identifiers the inventory UI needs to render anything at all.
+!data/items-english.json
+static/items/

Dockerfile

@@ -0,0 +1,46 @@
+# PSFPortal — Vite/React frontend built and served by the Express API.
+#
+# Debian (glibc) base. This used to be load-bearing -- `bcrypt` and `pg` are
+# native modules, and bcrypt's glibc prebuilts avoided a source build. Both are
+# gone now that the login server owns the database and the password check, so
+# the dependency tree is pure JavaScript and an Alpine base would work. Left on
+# Debian deliberately rather than swapped in passing: the saving is tens of
+# megabytes on a locally-built dev image, and a base change deserves its own
+# test. npm install still runs inside the image so the tree matches the
+# container platform (the host may be Windows/macOS).
+
+# ---- build stage: install deps and produce the static SPA in public/ ----
+FROM node:24-bookworm-slim AS build
+WORKDIR /app
+
+# package-lock.json is gitignored in this project, so install rather than ci.
+COPY package.json ./
+RUN npm install
+
+COPY . .
+# Client-derived assets (data/) are gitignored and absent from a clean checkout, so create the
+# directory unconditionally -- otherwise the runtime COPY below fails on a fresh clone. An image
+# built WITHOUT them is fully functional, just showing internal object names and plain grid tiles.
+# NODE_ENV must be set for the BUILD, not just the runtime stage below: vite.config.ts gates source
+# maps on it, and a map emitted here would be copied into the image and served publicly.
+RUN mkdir -p data && NODE_ENV=production npm run build
+
+# ---- runtime stage: the Express server + built assets ----
+FROM node:24-bookworm-slim
+WORKDIR /app
+ENV NODE_ENV=production
+
+COPY --from=build /app/node_modules ./node_modules
+COPY --from=build /app/public ./public
+COPY --from=build /app/api ./api
+# Item names/icons generated from a local client install (see docs/client-assets.md). Present only
+# when the builder supplied them; the app falls back to internal names and plain tiles otherwise.
+# NOTE: an image built with these baked in carries Daybreak-owned material -- keep it local, do not
+# push it to a public registry.
+COPY --from=build /app/data ./data
+COPY --from=build /app/index.ts ./index.ts
+COPY --from=build /app/package.json ./package.json
+
+EXPOSE 8080
+# The Express server is TypeScript run directly by Node (native type stripping); no build step.
+CMD ["node", "index.ts"]