lumbridge-public/tera
Archived
1
0
Fork 0
Code Activity

Both doors get a share card, and they are not the same card

Browse Source 
A link to tera.lumbridgecorp.com or office.lumbridgecorp.com unfurled as a bare
blue URL. No picture, no sentence, and a title — "Lumbridge Simulate — San
Francisco" — that was wrong at one of the two doors and stale at the other.
There were no `og:` or `twitter:` tags in the document at all. For a project
whose entire pitch is that you should look at it, that is the most expensive
missing markup in the repo.

Both cards are screenshots of the running app, not drawings of it, and that is
the load-bearing decision rather than a shortcut. `scripts/brand-assets/` builds
them in two passes: shoot the city and the office out of `dist/`, then render
`og.html` over those shots at exactly 1200x630. The thing is worth looking at,
and a drawing of it goes stale in silence — which is not hypothetical. The card
currently live on lumbridgecorp.com is a viewport screenshot of a marketing page
that has since been rewritten, so that preview advertises a positioning the site
no longer uses, and it has been doing so for a month with nobody noticing. A
card regenerated from `dist/` by one command is a card that can be kept true by
running the command.

The clock is shifted to midday for the capture, because the sun is real —
`observe()` computes it from `new Date()` — and a card regenerated at two in the
morning is an honest photograph of a black rectangle. Shifted rather than
frozen: everything else runs off `requestAnimationFrame`, and a stopped clock
stalls the frame loop the screenshot is waiting on.

Every string on the cards is the project's own. The headlines are what
`README.md` already says each half is; "Clone it and it works" is CONTRACT.md
§0's acceptance test in the words `main.ts` uses for it; the licence in the
corner is the one in the repo root. A share card is the most-read and least
reviewed sentence a project has, which is exactly why it should not be where new
claims get invented.

The harder half was that the two doors are one bundle. The app sorts out which
door it is by reading its own hostname; a crawler cannot, because it reads the
HTML and nothing else — so one `index.html` means both doors unfurl as the same
place, and being a different place is the office door's whole reason to exist. A
second hand-written shell is what the Caddy config already argues against for the
static root ("sharing the root rather than copying it means a deploy cannot leave
the two doors on different builds"), and two 900-line files each carrying the
inline stylesheet would drift on the first CSS change with nothing to notice.

So the build emits both. Everything outside the `ogc:` markers is copied byte for
byte — verified: `office.html` and `index.html` are identical below `</head>` and
point at the same bundle hash — and only the head block differs. A change to the
interface reaches both doors by construction. It runs in `writeBundle` rather
than `transformIndexHtml` because it needs the finished document, after Vite has
rewritten the asset URLs, and it errors rather than no-oping if the markers go
missing: a card that is quietly the wrong one is the failure the plugin exists to
prevent.

`deploy/Caddyfile.snippet` documents the one line that turns it on — the office
door's `try_files` fallback pointing at `/office.html` off the same shared root.
A deployment that skips it is not broken; the office door keeps working and
unfurls with the city's card, which is what it did before.

Not deployed. The live Caddyfile still falls back to /index.html for the office
host, so this needs that one-line change on cloud-2 before office.
lumbridgecorp.com unfurls as the office.

Both shells boot clean in Chrome with zero console errors, 31 client tests and
the no-binary gate still pass — `public/` is exempt from it, which is where the
two PNGs live.
This commit is contained in:
Kartios
2026-08-06 03:07:00 -07:00
parent aab58a1c24
commit 37d5320664
8 changed files with 565 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vite.config.ts
+103 -1
View File
@@ -1,9 +1,107 @@
import { defineConfig } from "vite";
import { readFile, writeFile } from "node:fs/promises";
import { join } from "node:path";
import { defineConfig, type Plugin } from "vite";
/**
* The office's copy of the page, emitted from the city's.
*
* `office.lumbridgecorp.com` and `tera.lumbridgecorp.com` are one bundle behind
* two names, and the app works out which door it is at runtime by reading its
* own hostname. A crawler cannot: it reads the HTML and nothing else. So a
* single `index.html` means both doors unfurl with the same title, the same
* sentence and the same picture — and the office door's whole reason to exist is
* that it is a different place.
*
* The obvious fix, a second hand-written `office.html`, is the one the Caddy
* config already argues against for the static root: "sharing the root rather
* than copying it means a deploy cannot leave the two doors on different
* builds". Two 900-line files each carrying the whole inline stylesheet would
* drift on the first CSS change, and nothing would notice, because the drift is
* invisible until somebody opens the other door.
*
* So there is one source and the build emits both shells. Everything outside the
* `ogc:` markers in `index.html` is copied byte for byte — the stylesheet, the
* DOM, the script tag Vite has already rewritten to the hashed bundle — and only
* the block between them is replaced. A change to the interface reaches both
* doors by construction, and the only thing that can differ is the thing that is
* supposed to.
*
* It runs in `writeBundle` rather than `transformIndexHtml` because it needs the
* *finished* document, after Vite has substituted the asset URLs. Transforming
* earlier would emit a page pointing at unhashed source paths.
*/
function twoDoors(): Plugin {
const MARKER_END = "<!-- ogc:end -->";
const OFFICE = `
<title>Spaces — an office you can walk around</title>
<meta
name="description"
content="Lumbridge HQ, one floor: the rooms, the desks and who is at them. Rendered in the browser from a data file anybody can copy. Apache-2.0, self-hostable."
/>
<link rel="canonical" href="https://office.lumbridgecorp.com/" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Lumbridge Spaces" />
<meta property="og:title" content="Spaces — an office you can walk around" />
<meta
property="og:description"
content="The rooms, the desks and who is at them — one floor plan, rendered from a data file anybody can copy."
/>
<meta property="og:url" content="https://office.lumbridgecorp.com/" />
<meta property="og:image" content="https://office.lumbridgecorp.com/og-office.png" />
<meta property="og:image:type" content="image/png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta
property="og:image:alt"
content="Lumbridge HQ seen from above as a cutaway model, desks and meeting rooms visible, people at their seats."
/>
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Spaces — an office you can walk around" />
<meta
name="twitter:description"
content="The rooms, the desks and who is at them — one floor plan, rendered from a data file anybody can copy."
/>
<meta name="twitter:image" content="https://office.lumbridgecorp.com/og-office.png" />`;
return {
name: "lumbridge:two-doors",
apply: "build",
async writeBundle(options) {
const dir = options.dir ?? "dist";
const html = await readFile(join(dir, "index.html"), "utf8");
const open = html.indexOf("ogc:start");
const end = html.indexOf(MARKER_END);
// Loudly, rather than by silently shipping two identical shells. A card
// that is quietly the wrong one is the failure this plugin exists to
// prevent, so losing the markers must not be a no-op.
if (open === -1 || end === -1) {
this.error("index.html has no ogc:start/ogc:end markers — cannot emit office.html");
return;
}
// The opening marker sits inside a larger comment, so cut from the start
// of that comment: otherwise the explanation ships on both doors while
// being true of only one.
const from = html.lastIndexOf("<!--", open);
const office =
html.slice(0, from) +
"<!-- The office door. Generated from index.html by `twoDoors` in vite.config.ts. -->" +
OFFICE +
html.slice(end + MARKER_END.length);
await writeFile(join(dir, "office.html"), office, "utf8");
},
};
}
export default defineConfig({
// Mounted under tera.lumbridgecorp.com in production; the trailing
// slash matters, since every asset URL is resolved against it.
base: process.env.TERA_BASE ?? "/",
plugins: [twoDoors()],
build: {
outDir: "dist",
target: "es2022",
@@ -11,6 +109,10 @@ export default defineConfig({
// verbatim — so `import.meta.env` was never substituted there and the page
// could not be told which identity provider to sign in against. It is a real
// entry now; the built URL (`/login.html`) is unchanged.
//
// `office.html` is deliberately not a third entry: it is the same document
// as `index.html` with a different head, so making it one would give it its
// own copy of the bundle graph. It is emitted after the build instead.
rollupOptions: { input: { index: "index.html", login: "login.html" } },
},
});