@open-commune/web 0.1.5 → 0.2.0

package/README.md

@@ -36,6 +36,19 @@ Run it with Bun: the database layer uses `bun:sqlite`, so `bun --bun nuxt dev`,
 
 Environment is validated at startup by `@open-commune/core`; see `.env.example` in the repository for the full list.
 
+One variable matters when you deploy a build rather than run it in place. Nitro
+inlines the core into its chunks, but the Drizzle migrations are files: the
+build drops them next to the server output, and the deployment points at them.
+
+```
+COMMUN_MIGRATIONS_DIR=/path/to/.output/drizzle
+```
+
+Leave it unset in development — the layer resolves the folder from the
+installed `@open-commune/core`. Unset in a deployment where `node_modules` is
+gone, migrations are silently skipped and the first query fails on a missing
+table.
+
 ## Licence
 
 AGPL-3.0-or-later.

package/components/forms/inputs/input-editor.vue

@@ -3,7 +3,7 @@
     <label v-if="label" :for="name" class="block text-2xs font-light tracking-wider text-gray-500 uppercase">
       {{ label }}
     </label>
-    <!-- Fixed toolbar, same layout as the legacy editor: discoverability for
+    <!-- Fixed toolbar: discoverability for
          authors who never hover a handle or type "/". Gestures stay available. -->
     <UEditorToolbar
       v-if="uEditor?.editor"
@@ -149,9 +149,8 @@
 // contract (shared cache, bounded resolution). Editing surface is
 // Notion-like: selection bubble, slash commands, per-block drag handle.
 //
-// TRANSITIONAL value contract: accepts the ProseMirror object (target) or
-// the legacy stringified JSON, and emits IN THE SAME SHAPE it received —
-// the string adapter dies with models/_commun.
+// Value contract: accepts the ProseMirror document as an object or as
+// stringified JSON, and emits IN THE SAME SHAPE it received.
 import { ref, watch } from 'vue'
 import { mapEditorItems } from '@nuxt/ui/utils/editor'
 import { communExtensions, communStarterKit, sanitizeDoc, EMBED_SERVICES } from '~/editor'
@@ -304,7 +303,7 @@ const slashItems = [
   ],
 ]
 
-// Fixed toolbar: the legacy composition — block catalog, link, marks, alignment.
+// Fixed toolbar: block catalog, link, marks, alignment.
 const toolbarItems = [
   [{ slot: 'blocks' }],
   [

package/nuxt.config.ts

@@ -1,5 +1,7 @@
 import { globSync } from 'node:fs';
-import { dirname, join, resolve } from 'node:path';
+import { cp } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+import { createRequire } from 'node:module';
 import { fileURLToPath } from 'node:url';
 
 // Under Bun's isolated store, the ESM build of @vue/devtools-api only exists
@@ -32,13 +34,21 @@ const devtoolsApiEsm = findDevtoolsApiEsm();
 // found.
 const layerDir = dirname(fileURLToPath(import.meta.url));
 
-// Le worker de dev empaquette les sources du core, donc le dossier de
-// migrations Drizzle n'y est pas resolvable relativement — on l'epingle ici,
-// ou le chemin est connu. (Repris de l'ancien apps/api/nitro.config.ts.)
-process.env.COMMUN_MIGRATIONS_DIR ??= resolve(
-  fileURLToPath(new URL('.', import.meta.url)),
-  '../../packages/core/drizzle',
-);
+// Le worker de dev empaquette les sources du core : le dossier de migrations
+// Drizzle n'y est plus resolvable relativement, on l'epingle ici. Par
+// resolution de module et NON par chemin relatif — « ../../packages/core »
+// n'est vrai que dans le monorepo, jamais chez qui installe la couche.
+function coreDrizzleDir(): string | undefined {
+  try {
+    const pkg = createRequire(import.meta.url).resolve('@open-commune/core/package.json');
+    return join(dirname(pkg), 'drizzle');
+  } catch {
+    return undefined;
+  }
+}
+
+const drizzleDir = coreDrizzleDir();
+if (drizzleDir) process.env.COMMUN_MIGRATIONS_DIR ??= drizzleDir;
 
 // https://nuxt.com/docs/api/configuration/nuxt-config
 export default defineNuxtConfig({
@@ -75,6 +85,15 @@ export default defineNuxtConfig({
     scheduledTasks: {
       '30 0 * * *': ['deploy'],
     },
+    hooks: {
+      // Nitro inline le core dans ses chunks : le dossier de migrations, lui,
+      // ne suit pas. On le depose a cote du build pour qu'il voyage avec, et
+      // le deploiement pointe COMMUN_MIGRATIONS_DIR dessus (l'image le fait).
+      async compiled(nitro) {
+        if (!drizzleDir) return;
+        await cp(drizzleDir, join(nitro.options.output.dir, 'drizzle'), { recursive: true });
+      },
+    },
   },
   css: [join(layerDir, 'assets/css/main.css')],
   // Scan nested composables (composables/core/domains/*).

package/package.json

@@ -17,7 +17,7 @@
     "@iconify/vue": "^5.0.1",
     "@nuxt/kit": "^4.5.1",
     "@nuxt/ui": "^4.3.0",
-    "@open-commune/core": "^0.1.4",
+    "@open-commune/core": "^0.2.0",
     "@open-commune/editor": "^0.1.4",
     "@pinia-orm/nuxt": "^2.0.0",
     "@pinia/nuxt": "^1.0.1",
@@ -40,7 +40,7 @@
   },
   "description": "The Open Commune application: the admin interface and the server, on a single origin.",
   "license": "AGPL-3.0-or-later",
-  "version": "0.1.5",
+  "version": "0.2.0",
   "type": "module",
   "main": "./nuxt.config.ts",
   "files": [

package/pages/index/index.vue

@@ -23,11 +23,6 @@
       />
       <button-primary type="submit" label="S'identifier" :loading="isLoading" class="w-full" />
     </form>
-    <!-- Le lien de réinitialisation était commenté depuis le legacy, qui
-         n'envoyait AUCUN email : le seul recours était le formulaire de
-         support. L'événement `passwordResetRequested` étant désormais relayé
-         vers un fournisseur d'emails, le parcours autonome reprend sa place —
-         et Fillout redevient ce qu'il doit être, un second recours. -->
     <div class="flex mt-8 flex-col items-center justify-center">
       <button-tertiary
         label="Vous avez oublié votre mot de passe ?"

package/server/api/v1/content/deployment.get.ts

@@ -1,45 +0,0 @@
-import { createError, defineEventHandler } from 'h3';
-import { useCore } from '../../../utils/core.ts';
-
-/**
- * Legacy-compatible plane: the payload current site builds consume —
- * `_theme` (visual identity), `_pages` (page definitions) and `slugs`
- * (static paths plus every published `/collection/slug`).
- */
-export default defineEventHandler(async () => {
-  const { organization, collections, media } = useCore().services;
-
-  const settings = await organization.get();
-  if (!settings)
-    throw createError({ statusCode: 404, statusMessage: 'organization not initialized' });
-
-  const deployment = (settings.deployment ?? {}) as {
-    theme?: unknown;
-    definition?: Array<{ path?: string }>;
-    sort?: unknown;
-  };
-  // The theme lives under deployment.theme; older records may still carry it
-  // under settings.theme, hence the fallback below.
-  const theme =
-    deployment.theme ?? (settings.settings as { theme?: unknown } | null)?.theme ?? undefined;
-  const pageSlugs = (deployment.definition ?? [])
-    .map((page) => page.path ?? '')
-    .filter((path) => path && !path.includes(':'));
-
-  return {
-    name: 'success',
-    description: 'Action succeed.',
-    data: {
-      // The organisation's imported identifier, when it has one.
-      _id: (settings.legacyExtra as { legacyId?: string } | null)?.legacyId ?? settings.id,
-      name: settings.name,
-      ...(deployment.sort !== undefined ? { sort: deployment.sort } : {}),
-      // Iso legacy `_parseRecursively` : les chaînes `_media:<id>` de _theme/_pages
-      // sont remplacées par le média signé. Clé OMISE quand le thème est absent
-      // (an organisation may have no deployment.theme at all).
-      ...(theme !== undefined ? { _theme: await media.resolveMediaPlaceholders(theme) } : {}),
-      _pages: await media.resolveMediaPlaceholders(deployment.definition ?? []),
-      slugs: [...pageSlugs, ...(await collections.publishedSlugs())],
-    },
-  };
-});

package/server/api/v1/content/records.get.ts

@@ -1,12 +0,0 @@
-import { defineEventHandler } from 'h3';
-import { useCore } from '../../../utils/core.ts';
-
-/**
- * Legacy-compatible plane: the current site builds call this exact path.
- * Flat map of published entries keyed by id, media resolved, wrapped in the
- * `{ name, description, data }` envelope those clients expect.
- */
-export default defineEventHandler(async () => {
-  const records = await useCore().services.collections.legacyRecordsPayload();
-  return { name: 'success', description: 'Action succeed.', data: { records } };
-});

package/server/middleware/3.api-token.ts

@@ -1,20 +0,0 @@
-import { createError, defineEventHandler, getRequestHeader, getRequestURL } from 'h3';
-import { useCore } from '../utils/core.ts';
-
-/**
- * API-token guard of the public content plane; runs after `2.session`.
- *
- * Accepts both `Authorization: Bearer <token>` and the bare
- * `Authorization: <token>` form that existing site builds send.
- */
-const GUARDED_PATHS = new Set(['/api/v1/content/records', '/api/v1/content/deployment']);
-
-export default defineEventHandler(async (event) => {
-  if (!GUARDED_PATHS.has(getRequestURL(event).pathname)) return;
-
-  const auth = getRequestHeader(event, 'authorization') ?? '';
-  const token = auth.startsWith('Bearer ') ? auth.slice('Bearer '.length) : auth;
-  if (!token || !(await useCore().services.users.verifyApiToken(token))) {
-    throw createError({ statusCode: 401, statusMessage: 'missing or invalid API token' });
-  }
-});