kempo 4.2.40 → 4.4.0

package/server/db/schema.js

@@ -1,4 +1,4 @@
-import { pgTable, text, timestamp, boolean, index, jsonb } from 'drizzle-orm/pg-core';
+import { pgTable, text, timestamp, boolean, index, jsonb, bigserial, bigint } from 'drizzle-orm/pg-core';
 
 /*
   Auth Tables
@@ -114,6 +114,35 @@ export const extension = pgTable('extension', {
   updatedAt: timestamp('updatedAt').notNull(),
 });
 
+/*
+  Realtime System
+*/
+
+/*
+  A published message, kept only for channels that opt in to persistence. `id` is what a client
+  hands back as `since` to replay what it missed, so it must be ordered within a channel: publish
+  takes a per-channel lock, otherwise two rows could commit out of id order and a replay from the
+  earlier id would skip the later-committing one for good.
+*/
+export const realtimeMessage = pgTable('realtimeMessage', {
+  id: bigserial('id', { mode: 'number' }).primaryKey(),
+  channel: text('channel').notNull(),
+  data: jsonb('data').notNull(),
+  createdAt: timestamp('createdAt').notNull(),
+}, table => [
+  index('realtimeMessage_channel_id_idx').on(table.channel, table.id),
+  index('realtimeMessage_createdAt_idx').on(table.createdAt),
+]);
+
+/*
+  How far a channel has been pruned. Ids are shared across channels, so a gap cannot be inferred from
+  id arithmetic; a client whose `since` is below this watermark has provably missed messages.
+*/
+export const realtimeChannel = pgTable('realtimeChannel', {
+  channel: text('channel').primaryKey(),
+  prunedThrough: bigint('prunedThrough', { mode: 'number' }).notNull().default(0),
+});
+
 /*
   Triggers to prevent deletion of system resources
 */

package/server/sdk.js

@@ -196,3 +196,8 @@ export { default as listExtensions } from './utils/extensions/listExtensions.js'
 export { default as uninstallExtension } from './utils/extensions/uninstallExtension.js';
 export { default as updateExtension } from './utils/extensions/updateExtension.js';
 
+/*
+  Realtime
+*/
+
+export * as realtime from './utils/realtime/index.js';

package/server/utils/extensions/contentDirs.js

@@ -0,0 +1,27 @@
+import { join } from 'path';
+import { getEnabledExtensions } from './scopeCache.js';
+
+const NODE_MODULES = join(process.cwd(), 'node_modules');
+
+/*
+  The directories an enabled extension may contribute *.global.html and *.fragment.html from, split
+  by which half of the site is rendering: `admin/` for the admin portal, `public/` for the live site.
+
+  Each is read straight from the package at render time, the same way an extension's pages and
+  routes are resolved, so nothing is copied anywhere on install: enabling, disabling, upgrading or
+  removing an extension takes effect immediately, and there is nothing left behind to clean up.
+
+  That is also the whole of the on/off switch for this content — a disabled extension drops out of
+  these lists and its files are simply never read. There is no `enabled` flag on a packaged file the
+  way there is on admin-authored global content, because there is no stored row to carry one.
+
+  Lives here rather than in middleware/kempo.js so that server utils can reach it too — the 404 page
+  is rendered from server/utils/routing/serveUnmatched.js, and importing the middleware from there
+  would be circular.
+*/
+const extensionDirs = async sub =>
+  (await getEnabledExtensions()).map(ext => join(NODE_MODULES, ext.name, sub));
+
+export const extensionAdminDirs = () => extensionDirs('admin');
+
+export const extensionPublicDirs = () => extensionDirs('public');