Files
fofos-admin/db/schema.ts
T
pastilhasandClaude Opus 5 a1fe543dff two database names, and a button that creates what is missing
Production and development, stored as NAMES rather than URLs. The site runs on
the same Postgres Officer is already connected to — that is the whole reason a
name is enough — and a URL here would be a second copy of a host, a port and a
credential that already exist in the platform's configuration, free to drift
from it and free to point at another machine.

Naming and creating are separate, and were worth two buttons. A database that
already exists still needs its name recorded, and making Create the only way to
save would leave nobody able to point the site at something already set up. The
tick beside each field comes from pg_database, not from what was typed — the
useful question is whether the thing exists, and that came apart from "somebody
saved a name" the moment the two actions split.

CREATE DATABASE cannot be parameterised, so the name goes into the statement as
text and the identifier check is the entire security boundary. It is therefore
strict rather than accommodating — lowercase, leading letter or underscore,
nothing else — and it is re-run immediately before the statement is built,
because the gap between storing a name and using it is exactly where a check
that happened earlier stops being a check. Postgres folds unquoted identifiers
to lowercase, so accepting `Fofos` would create `fofos` and then report a name
nobody could find; refusing is kinder than silently changing it.

Officer's own database and the Postgres templates are refused outright. Pointing
the site at Officer's database would not read as a configuration mistake — it
would read as the platform corrupting itself.

Nothing here drops a database, and nothing should: `fofos_website` and
`fofos_old` are one keystroke apart and one of them holds the client's site.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-29 12:06:40 +01:00

110 lines
5.3 KiB
TypeScript

import { pgTable, serial, text, timestamp, integer } from 'drizzle-orm/pg-core';
/**
* The connection to the fofos server. One row, and the ONLY thing this plugin stores.
*
* ── Why there is nothing else here ──
*
* Every temptation to add a table to this file should be resisted, and it is worth writing down why
* rather than relying on taste. fofos owns its own Postgres and its own media store; this plugin
* reaches them over HTTP. If the client's collections and photographs lived here instead, they would
* live under Officer's plugin installer — which drops a plugin's tables when the "delete its data"
* checkbox is ticked.
*
* So the strongest thing that can be said about this plugin is a consequence of this file being one
* table long: **no operation on it can destroy the client's work.** Deleting it removes a URL and a
* token, and the site is untouched.
*
* A cache would be the thin end of it. If a panel ever needs one, it belongs in memory or in the
* browser, not in a table that outlives the request.
*
* ── Why not core `service_connections` ──
*
* It fits the shape — `url`, an encrypted `secret` — but its `ServiceName` is a closed TypeScript
* union, so using it means editing the platform to add a name, and a plugin should install into a
* platform it did not have to change. The same reasoning `plugins/proxy-manager/db/schema.ts` gives,
* and worth revisiting on the day that union opens.
*/
export const fofosAdminConnection = pgTable('fofos_admin_connection', {
id: serial('id').primaryKey(),
/** Where the fofos server is — the origin its API is served from. Normalised without a trailing slash. */
url: text('url').notNull(),
/**
* fofos's `FOFOS_API_TOKEN`, encrypted with `encryptSecret('fofos-admin', …)` — its own purpose
* key, so a leak of that one opens this column and nothing else.
*
* **Never returned across the API boundary**, at any level, to anybody, including the owner. A
* settings form asking "is one set" gets a boolean.
*
* There is exactly one of these rather than one per user, and that is not laziness: fofos has a
* single token and no notion of accounts. WHO is editing is a question Officer answers with its own
* accounts and permissions, in front of this.
*/
token: text('token').notNull(),
/** From the last successful probe — which sections that server says it serves. Diagnostic only. */
sections: text('sections').array(),
lastProbeAt: timestamp('last_probe_at', { withTimezone: true }),
/**
* `integer` rather than `boolean` for the same reason proxy-manager uses one: three states, not
* two. Null means never probed, which reads differently from probed-and-failed.
*/
lastProbeOk: integer('last_probe_ok'),
createdAt: timestamp('created_at', { withTimezone: true }).notNull().defaultNow(),
updatedAt: timestamp('updated_at', { withTimezone: true }).notNull().defaultNow(),
});
export type FofosAdminConnection = typeof fofosAdminConnection.$inferSelect;
/**
* Administration's own settings. One row, and nothing in it belongs to the client.
*
* ── Why a second table and not a column on the one above ──
*
* `fofos_admin_connection.url` and `.token` are both `notNull`, so a root path could not be saved
* without also having an HTTP connection — and that connection is being replaced, not extended. When
* it goes, its table is a clean `drop` rather than surgery on columns that outlived it.
*
* The rule at the top of this file still holds and this does not bend it: what is forbidden here is
* the CLIENT'S WORK — collections, photographs, copy. This row holds a path and, later, how to read
* fofos's own database. Deleting it loses a setting somebody can retype, never a thing they made.
*/
export const fofosAdminSettings = pgTable('fofos_admin_settings', {
id: serial('id').primaryKey(),
/**
* Where the fofos site lives on this machine. ABSOLUTE, always.
*
* Never `~/fofos`. A tilde means "whoever is asking", and the people asking will not all be the same
* person — this plugin is grantable, and a member reading this setting must see the one real
* directory the site is in rather than a path that resolves to their own home and is not there.
*
* Null means never set, and the default is computed at read time rather than written here. See
* `api/settings.ts` for why that is not the same as writing it once at install.
*/
rootPath: text('root_path'),
/**
* The two Postgres databases the site uses, by NAME.
*
* Names and not URLs, deliberately. They live on the same instance Officer is already connected to —
* that is the whole reason this is a name — so a URL here would be a second copy of a host, a port
* and a credential that already exist in the platform's own configuration, able to drift from it and
* able to point somewhere nobody intended.
*
* Null means not chosen yet. There is no default: a database name is not something to guess at, and
* a wrong guess here is a site reading somebody else's tables.
*/
dbProduction: text('db_production'),
dbDevelopment: text('db_development'),
createdAt: timestamp('created_at', { withTimezone: true }).notNull().defaultNow(),
updatedAt: timestamp('updated_at', { withTimezone: true }).notNull().defaultNow(),
});
export type FofosAdminSettings = typeof fofosAdminSettings.$inferSelect;