create-meith 0.26.1 → 0.28.0

package/dist/bin.mjs

@@ -23,7 +23,7 @@ var MATERIALIZED_AT_ROOT = [
   "tsconfig.json",
   "next-env.d.ts"
 ];
-var VERCEL_BUILD_COMMAND = `community migrate && forum-web build ${AT_ROOT_FLAG}`;
+var VERCEL_BUILD_COMMAND = `meith migrate && forum-web build ${AT_ROOT_FLAG}`;
 var TICK_PATH = "/api/system/tick";
 var TICK_SCHEDULE = "0 3 * * *";
 var RESEND_SENDER_MAILBOX = "noreply";
@@ -85,7 +85,7 @@ var ENV_DATABASE_URL_PROSE = `# Your Postgres connection string.
 # database rather than the cause. Your own Postgres, with a fixed number of
 # processes in front of it, does not need one.`;
 var ENV_DIRECT_DATABASE_URL_PROSE = `# The other half of that pair: the DIRECT (non-pooler) string, used only by
-# \`community migrate\` and \`community backup\`. Migrations hold a session-level
+# \`meith migrate\` and \`meith backup\`. Migrations hold a session-level
 # advisory lock so that two deploys landing together queue instead of both
 # applying the same migration, and a transaction-mode pooler cannot hold that
 # lock: it takes the connection back the moment the lock statement ends, which
@@ -213,7 +213,7 @@ DATABASE_URL=
 ${ENV_DIRECT_DATABASE_URL_PROSE}
 #
 # On Vercel this is not optional, and it is no longer yours to copy. DATABASE_URL
-# here is the pooler string, the build runs \`community migrate\` against it, and
+# here is the pooler string, the build runs \`meith migrate\` against it, and
 # /install takes the second of those two session locks on first run. Left blank,
 # the board reads Neon's own direct string \u2014 \`DATABASE_URL_UNPOOLED\` first, then
 # \`POSTGRES_URL_NON_POOLING\` \u2014 and refuses to boot if neither is there, naming
@@ -250,7 +250,7 @@ CRON_SECRET=
 #
 # BLOB_READ_WRITE_TOKEN is the other way in, and you make it yourself on the
 # store. Set it when something has to reach the store from OUTSIDE a Vercel
-# deployment \u2014 \`community backup\` run on your own machine is the case that
+# deployment \u2014 \`meith backup\` run on your own machine is the case that
 # matters \u2014 because there is no OIDC identity there to borrow. Set both and the
 # board prefers the store id, unless the token names a different store, in which
 # case the token wins: naming another store is a deliberate act.
@@ -401,7 +401,7 @@ function scaffold(options) {
           dev: `forum-web dev${atRootFlag}`,
           build: `forum-web build${atRootFlag}`,
           start: `forum-web start${atRootFlag}`,
-          community: "community"
+          meith: "meith"
         },
         dependencies: {
           "@meith/web": version,
@@ -473,25 +473,14 @@ export default defineForumConfig({
 `);
   files.set(
     "meith.plugins.ts",
-    `/**
- * The board's installed-plugin list.
- *
- * Inside the Meith monorepo this file is generated from board.plugins.json
- * by \`pnpm board:gen\` (see docs/customization/plugins.md) \u2014 that generator is
- * repository tooling, not something this workspace carries, so this file
- * starts as a plain, valid file with the same shape instead. Add a plugin by
- * importing its \`plugin\`/\`messages\` exports and adding an entry:
- *
- *   import { messages as greeterMessages, plugin as greeterPlugin } from '@meith/plugin-greeter'
- *
- *   export const INSTALLED_PLUGINS: readonly InstalledPlugin<PluginDefinition>[] = [
- *     { key: 'greeter', enabled: true, plugin: greeterPlugin, messages: greeterMessages },
- *   ]
- *
- * and the matching entry in board.plugins.json, which is what
- * \`community plugin:add\`/\`plugin:remove\` read inside the monorepo \u2014 kept
- * here too so the two files agree about what is installed.
- */
+    `// Generated from board.plugins.json by \`meith plugin:add\` and \`meith plugin:remove\`.
+//
+// The simple path is those commands, or editing board.plugins.json and running one of
+// them. A plugin that does not fit that convention can be added here by hand instead \u2014
+// keep it out of board.plugins.json so a regenerate does not drop it.
+//
+// docs/customization/plugins.md explains both.
+
 import type { InstalledPlugin } from '@meith/web/config'
 
 export const INSTALLED_PLUGINS: readonly InstalledPlugin[] = []
@@ -552,8 +541,8 @@ updates:
 # "Custom boards").
 #
 # Two stages, not three: unlike the official image, this does not prune down
-# to Next's own standalone output. The migrate role below runs \`community
-# migrate\`, and \`community\` materializes @meith/cli's sources and runs them
+# to Next's own standalone output. The migrate role below runs \`meith
+# migrate\`, and \`meith\` materializes @meith/cli's sources and runs them
 # with tsx at the moment it runs (see the meith repository's
 # docs/contributing/development.md, "Consuming the board from a workspace") \u2014 it needs
 # the full, un-pruned node_modules tree this board installed, not what Next
@@ -594,6 +583,23 @@ ENV PORT=3000
 ENV HOSTNAME=0.0.0.0
 EXPOSE 3000
 
+# Uploaded files \u2014 avatars, board images, attachments \u2014 land here, and the
+# compose file mounts the persistent "uploads" volume over this path. Creating
+# it in the image, owned by node, is what lets the fresh volume inherit that
+# ownership; UPLOADS_DIR gives the board an absolute path so the working
+# directory never decides where uploads go. Without both, uploads land on the
+# container's own layer and a redeploy discards them.
+ENV UPLOADS_DIR=/app/.uploads
+RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
+
+# \`meith <command>\` on PATH runs this board's own operator CLI \u2014 the same one
+# node_modules/.bin/meith is \u2014 so a Coolify terminal or \`docker compose exec web
+# meith ...\` needs no path. It cd's to /board so the CLI finds this board's
+# config, and overrides any wrapper an inherited base image installed, which
+# would target the board that image was built from, not this one.
+RUN printf '#!/bin/sh\\ncd /board\\nexec node_modules/.bin/meith "$@"\\n' > /usr/local/bin/meith \\
+  && chmod +x /usr/local/bin/meith
+
 # node:alpine already carries a non-root "node" user; the board's own files
 # are copied in as root above, so they need handing over before this drops
 # privilege.
@@ -628,8 +634,8 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 # of minutes rather than a cold toolchain build.
 #
 # Two stages, not three: unlike the official image, this does not prune down
-# to Next's own standalone output. The migrate role below runs \`community
-# migrate\`, and \`community\` materializes @meith/cli's sources and runs them
+# to Next's own standalone output. The migrate role below runs \`meith
+# migrate\`, and \`meith\` materializes @meith/cli's sources and runs them
 # with tsx at the moment it runs (see the meith repository's
 # docs/contributing/development.md, "Consuming the board from a workspace") \u2014 it needs
 # the full, un-pruned node_modules tree this board installed, not what Next
@@ -671,6 +677,23 @@ ENV PORT=3000
 ENV HOSTNAME=0.0.0.0
 EXPOSE 3000
 
+# Uploaded files \u2014 avatars, board images, attachments \u2014 land here, and the
+# compose file mounts the persistent "uploads" volume over this path. Creating
+# it in the image, owned by node, is what lets the fresh volume inherit that
+# ownership; UPLOADS_DIR gives the board an absolute path so the working
+# directory never decides where uploads go. Without both, uploads land on the
+# container's own layer and a redeploy discards them.
+ENV UPLOADS_DIR=/app/.uploads
+RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
+
+# \`meith <command>\` on PATH runs this board's own operator CLI \u2014 the same one
+# node_modules/.bin/meith is \u2014 so a Coolify terminal or \`docker compose exec web
+# meith ...\` needs no path. It cd's to /board so the CLI finds this board's
+# config, and overrides any wrapper an inherited base image installed, which
+# would target the board that image was built from, not this one.
+RUN printf '#!/bin/sh\\ncd /board\\nexec node_modules/.bin/meith "$@"\\n' > /usr/local/bin/meith \\
+  && chmod +x /usr/local/bin/meith
+
 # node:alpine already carries a non-root "node" user; the board's own files
 # are copied in as root above, so they need handing over before this drops
 # privilege.
@@ -699,22 +722,22 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 set -e
 
 # An explicit command wins over the role, the same as the official image \u2014
-# \`docker run <image> node_modules/.bin/community --help\` should still run
-# the CLI rather than silently starting the web server.
+# \`docker compose run --rm web meith --help\` (or \`exec\` into the running
+# container) should run the CLI rather than silently starting the web server.
 if [ "$#" -gt 0 ]; then
   exec "$@"
 fi
 
-case "\${COMMUNITY_ROLE:-web}" in
+case "\${MEITH_ROLE:-web}" in
   migrate)
     # Runs to completion and exits; compose's one-shot service waits on it.
-    exec node_modules/.bin/community migrate
+    exec node_modules/.bin/meith migrate
     ;;
   web)
     exec node_modules/.bin/forum-web start
     ;;
   *)
-    echo "Unknown COMMUNITY_ROLE: \${COMMUNITY_ROLE}. Expected 'web' or 'migrate'." >&2
+    echo "Unknown MEITH_ROLE: \${MEITH_ROLE}. Expected 'web' or 'migrate'." >&2
     exit 1
     ;;
 esac
@@ -728,7 +751,7 @@ esac
 # a health probe taken while it runs has no opinion.
 set -e
 
-if [ "\${COMMUNITY_ROLE:-web}" = "migrate" ]; then
+if [ "\${MEITH_ROLE:-web}" = "migrate" ]; then
   exit 0
 fi
 
@@ -865,7 +888,7 @@ services:
     build: .
     image: ${name}
     environment:
-      COMMUNITY_ROLE: migrate
+      MEITH_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
@@ -997,7 +1020,7 @@ services:
     # runs the old code.
     pull_policy: always
     environment:
-      COMMUNITY_ROLE: migrate
+      MEITH_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
@@ -1196,7 +1219,7 @@ Two things nothing configures for you, on either path:
   loop calling \`/api/system/tick\` once a minute, since \`@meith/web\`'s own
   worker package is not something a board outside the meith monorepo can
   depend on yet. Deploy some other way and something still has to call that
-  route (or run \`community task:run\`) every minute, or nothing catches up
+  route (or run \`meith task:run\`) every minute, or nothing catches up
   and nothing errors.
 
 ## Local
@@ -1214,8 +1237,8 @@ Posting needs Postgres. Copy \`.env.example\` to \`.env.local\`, set
 \`DATABASE_URL\` and the two secrets in it, then:
 
 \`\`\`sh
-npm run community -- migrate
-echo "<password>" | npm run community -- user:create --username <name> --email <address> --group administrators
+npm run meith -- migrate
+echo "<password>" | npm run meith -- user:create --username <name> --email <address> --group administrators
 \`\`\`
 
 ## Configuring
@@ -1226,9 +1249,43 @@ echo "<password>" | npm run community -- user:create --username <name> --email <
 - **\`/admin\`** \u2014 settings, forums, groups, members, themes, maintenance. An
   administrator re-enters their password to get in, and again for anything
   destructive.
-- **\`npm run community -- --help\`** \u2014 the operator CLI. Everything the panel does
+- **\`npm run meith -- --help\`** \u2014 the operator CLI. Everything the panel does
   and a few things it cannot, without a browser.
 
+## Installing plugins and themes
+
+Nothing installs into a running container \u2014 a plugin or theme has to be
+built into the image. In this repository:
+
+1. **Add it.** A **plugin** is one command, which installs the package and
+   registers it:
+
+   \`\`\`sh
+   npm run meith -- plugin:add @meith/plugin-dues
+   \`\`\`
+
+   It writes \`board.plugins.json\` and regenerates \`meith.plugins.ts\` for you
+   (\`npm run meith -- plugin:remove <key>\` reverses it). A **theme** is
+   \`npm install --save-exact @meith/theme-midnight\`, then an entry in
+   \`meith.config.ts\`'s \`themes\` map following the shape of the \`default\` one
+   already there \u2014 set \`defaultTheme\` to its key to make it the board's
+   default.
+
+2. **Commit and push**, then **Redeploy** from Coolify \u2014 pushing alone does
+   not rebuild. Quick start builds the new image on that redeploy; advanced/prebuilt
+   waits for \`.github/workflows/build.yml\` to finish first, and Redeploy is
+   what actually pulls the result.
+
+3. **If it ships database changes, apply them once it is up** \u2014 from
+   **Admin \u2192 System** (**Version & migrations**) in the browser, or:
+
+   \`\`\`sh
+   docker compose run --rm web meith upgrade
+   \`\`\`
+
+See [Installing plugins and themes](${repositoryUrl}/blob/main/docs/customization/installing.md)
+for the full guide.
+
 ## Upgrading
 
 \`\`\`sh
@@ -1269,7 +1326,7 @@ project's own \`.npmrc\` sets \`save-exact=true\` for the same reason, so an
 \`npm install\` of anything else here \u2014 a plugin, say \u2014 stays pinned too; the
 build workflow also refuses to build from anything but an exact version, as
 a second line of defense. Once the rebuilt image is deployed, run
-\`npm run community -- upgrade\` against it for the plugin migrations \u2014 see
+\`npm run meith -- upgrade\` against it for the plugin migrations \u2014 see
 [the operator CLI](${repositoryUrl}/blob/main/docs/guides/operations/operating.md#the-operator-cli)
 for running it against this deployment.
 
@@ -1512,9 +1569,9 @@ A board must stay movable, and the Blob store is the one part of this shape that
 is not portable: Neon and Upstash hand out ordinary Postgres and Redis strings
 that any host accepts, but a Vercel Blob store is reachable only through Vercel's
 own API and there is no bucket to sync out of it. **The uploads are the thing you
-have to carry out deliberately, and \`community backup\` is how.**
+have to carry out deliberately, and \`meith backup\` is how.**
 
-Under \`FILESTORE_DRIVER=blob\`, \`community backup\` includes the uploads **by
+Under \`FILESTORE_DRIVER=blob\`, \`meith backup\` includes the uploads **by
 default** \u2014 it walks the Blob store, pulls every object, and puts them in the
 bundle beside the database dump. This is the opposite of the \`s3\` default, which
 skips them, because a bucket has its own backup story you can drive yourself and
@@ -1525,7 +1582,7 @@ DATABASE_URL=\u2026            # Neon's pooled string
 DIRECT_DATABASE_URL=\u2026     # Neon's DATABASE_URL_UNPOOLED
 FILESTORE_DRIVER=blob
 BLOB_READ_WRITE_TOKEN=\u2026   # create one on the store; see below
-npm run community -- backup
+npm run meith -- backup
 \`\`\`
 
 Run that from a checkout of this repository, with those four values in the
@@ -1546,10 +1603,10 @@ so the same bundle moves the board either onward or away:
 
 \`\`\`sh
 # onto a self-hosted board with a bucket
-FILESTORE_DRIVER=s3 S3_BUCKET=\u2026 RESTORE_DATABASE_URL=\u2026 npm run community -- restore bundle.tar.gz
+FILESTORE_DRIVER=s3 S3_BUCKET=\u2026 RESTORE_DATABASE_URL=\u2026 npm run meith -- restore bundle.tar.gz
 
 # onto a board that keeps uploads on its own disk
-RESTORE_DATABASE_URL=\u2026 npm run community -- restore bundle.tar.gz --uploads-dir ./uploads
+RESTORE_DATABASE_URL=\u2026 npm run meith -- restore bundle.tar.gz --uploads-dir ./uploads
 \`\`\`
 
 Take one before you need it. A Blob store deleted with the Vercel project takes
@@ -1893,7 +1950,7 @@ and add the matching entry to \`board.plugins.json\`:
     { "plugins": [{ "key": "${name}", "package": "${name}", "enabled": true }] }
 
 Rebuild the board (\`npm run build\`) and, because this plugin ships a
-migration, run \`npx community migrate\`. The plugin then appears under
+migration, run \`npx meith migrate\`. The plugin then appears under
 **Admin \u2192 Plugins**.
 
 ## Publish and list it
@@ -2152,7 +2209,7 @@ async function run(argv, version) {
       ...kind === null ? [
         "Then set DATABASE_URL, AUTH_SECRET and TICK_SECRET and deploy.",
         "Something must run the tick every minute \u2014 the worker process, or",
-        "`community task:run`. Without it nothing catches up, and nothing errors."
+        "`meith task:run`. Without it nothing catches up, and nothing errors."
       ] : [
         `Then follow README.md \u2014 it walks through running the ${kind} inside a`,
         "scaffolded board and submitting it to the meith.dev marketplace."
@@ -2162,7 +2219,7 @@ async function run(argv, version) {
 }
 
 // src/bin.ts
-var result = await run(process.argv.slice(2), "0.26.1");
+var result = await run(process.argv.slice(2), "0.28.0");
 for (const line of result.lines) {
   if (result.code === 0) console.log(line);
   else console.error(line);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-meith",
-  "version": "0.26.1",
+  "version": "0.28.0",
   "description": "Scaffold a Meith board, plugin or theme — npx create-meith <name> writes a deployable board workspace; --plugin and --theme write extension workspaces built on the published kits.",
   "license": "MIT",
   "repository": {

package/src/bin.ts

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import { run } from './cli'
 
-const result = await run(process.argv.slice(2), '0.26.1')
+const result = await run(process.argv.slice(2), '0.28.0')
 for (const line of result.lines) {
   if (result.code === 0) console.log(line)
   else console.error(line)

package/src/cli.ts

@@ -145,7 +145,7 @@ export async function run(argv: readonly string[], version: string): Promise<Cli
         ? [
             'Then set DATABASE_URL, AUTH_SECRET and TICK_SECRET and deploy.',
             'Something must run the tick every minute — the worker process, or',
-            '`community task:run`. Without it nothing catches up, and nothing errors.',
+            '`meith task:run`. Without it nothing catches up, and nothing errors.',
           ]
         : [
             `Then follow README.md — it walks through running the ${kind} inside a`,

package/src/scaffold-extension.ts

@@ -206,7 +206,7 @@ and add the matching entry to \`board.plugins.json\`:
     { "plugins": [{ "key": "${name}", "package": "${name}", "enabled": true }] }
 
 Rebuild the board (\`npm run build\`) and, because this plugin ships a
-migration, run \`npx community migrate\`. The plugin then appears under
+migration, run \`npx meith migrate\`. The plugin then appears under
 **Admin → Plugins**.
 
 ## Publish and list it

package/src/scaffold.ts

@@ -29,7 +29,7 @@ export const MATERIALIZED_AT_ROOT = [
   'next-env.d.ts',
 ]
 
-export const VERCEL_BUILD_COMMAND = `community migrate && forum-web build ${AT_ROOT_FLAG}`
+export const VERCEL_BUILD_COMMAND = `meith migrate && forum-web build ${AT_ROOT_FLAG}`
 
 export const TICK_PATH = '/api/system/tick'
 
@@ -103,7 +103,7 @@ const ENV_DATABASE_URL_PROSE = `# Your Postgres connection string.
 # processes in front of it, does not need one.`
 
 const ENV_DIRECT_DATABASE_URL_PROSE = `# The other half of that pair: the DIRECT (non-pooler) string, used only by
-# \`community migrate\` and \`community backup\`. Migrations hold a session-level
+# \`meith migrate\` and \`meith backup\`. Migrations hold a session-level
 # advisory lock so that two deploys landing together queue instead of both
 # applying the same migration, and a transaction-mode pooler cannot hold that
 # lock: it takes the connection back the moment the lock statement ends, which
@@ -238,7 +238,7 @@ DATABASE_URL=
 ${ENV_DIRECT_DATABASE_URL_PROSE}
 #
 # On Vercel this is not optional, and it is no longer yours to copy. DATABASE_URL
-# here is the pooler string, the build runs \`community migrate\` against it, and
+# here is the pooler string, the build runs \`meith migrate\` against it, and
 # /install takes the second of those two session locks on first run. Left blank,
 # the board reads Neon's own direct string — \`DATABASE_URL_UNPOOLED\` first, then
 # \`POSTGRES_URL_NON_POOLING\` — and refuses to boot if neither is there, naming
@@ -275,7 +275,7 @@ CRON_SECRET=
 #
 # BLOB_READ_WRITE_TOKEN is the other way in, and you make it yourself on the
 # store. Set it when something has to reach the store from OUTSIDE a Vercel
-# deployment — \`community backup\` run on your own machine is the case that
+# deployment — \`meith backup\` run on your own machine is the case that
 # matters — because there is no OIDC identity there to borrow. Set both and the
 # board prefers the store id, unless the token names a different store, in which
 # case the token wins: naming another store is a deliberate act.
@@ -435,7 +435,7 @@ export function scaffold(options: ScaffoldOptions): ReadonlyMap<string, string>
           dev: `forum-web dev${atRootFlag}`,
           build: `forum-web build${atRootFlag}`,
           start: `forum-web start${atRootFlag}`,
-          community: 'community',
+          meith: 'meith',
         },
         dependencies: {
           '@meith/web': version,
@@ -509,25 +509,14 @@ export default defineForumConfig({
 
   files.set(
     'meith.plugins.ts',
-    `/**
- * The board's installed-plugin list.
- *
- * Inside the Meith monorepo this file is generated from board.plugins.json
- * by \`pnpm board:gen\` (see docs/customization/plugins.md) — that generator is
- * repository tooling, not something this workspace carries, so this file
- * starts as a plain, valid file with the same shape instead. Add a plugin by
- * importing its \`plugin\`/\`messages\` exports and adding an entry:
- *
- *   import { messages as greeterMessages, plugin as greeterPlugin } from '@meith/plugin-greeter'
- *
- *   export const INSTALLED_PLUGINS: readonly InstalledPlugin<PluginDefinition>[] = [
- *     { key: 'greeter', enabled: true, plugin: greeterPlugin, messages: greeterMessages },
- *   ]
- *
- * and the matching entry in board.plugins.json, which is what
- * \`community plugin:add\`/\`plugin:remove\` read inside the monorepo — kept
- * here too so the two files agree about what is installed.
- */
+    `// Generated from board.plugins.json by \`meith plugin:add\` and \`meith plugin:remove\`.
+//
+// The simple path is those commands, or editing board.plugins.json and running one of
+// them. A plugin that does not fit that convention can be added here by hand instead —
+// keep it out of board.plugins.json so a regenerate does not drop it.
+//
+// docs/customization/plugins.md explains both.
+
 import type { InstalledPlugin } from '@meith/web/config'
 
 export const INSTALLED_PLUGINS: readonly InstalledPlugin[] = []
@@ -592,8 +581,8 @@ updates:
 # "Custom boards").
 #
 # Two stages, not three: unlike the official image, this does not prune down
-# to Next's own standalone output. The migrate role below runs \`community
-# migrate\`, and \`community\` materializes @meith/cli's sources and runs them
+# to Next's own standalone output. The migrate role below runs \`meith
+# migrate\`, and \`meith\` materializes @meith/cli's sources and runs them
 # with tsx at the moment it runs (see the meith repository's
 # docs/contributing/development.md, "Consuming the board from a workspace") — it needs
 # the full, un-pruned node_modules tree this board installed, not what Next
@@ -634,6 +623,23 @@ ENV PORT=3000
 ENV HOSTNAME=0.0.0.0
 EXPOSE 3000
 
+# Uploaded files — avatars, board images, attachments — land here, and the
+# compose file mounts the persistent "uploads" volume over this path. Creating
+# it in the image, owned by node, is what lets the fresh volume inherit that
+# ownership; UPLOADS_DIR gives the board an absolute path so the working
+# directory never decides where uploads go. Without both, uploads land on the
+# container's own layer and a redeploy discards them.
+ENV UPLOADS_DIR=/app/.uploads
+RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
+
+# \`meith <command>\` on PATH runs this board's own operator CLI — the same one
+# node_modules/.bin/meith is — so a Coolify terminal or \`docker compose exec web
+# meith ...\` needs no path. It cd's to /board so the CLI finds this board's
+# config, and overrides any wrapper an inherited base image installed, which
+# would target the board that image was built from, not this one.
+RUN printf '#!/bin/sh\\ncd /board\\nexec node_modules/.bin/meith "$@"\\n' > /usr/local/bin/meith \\
+  && chmod +x /usr/local/bin/meith
+
 # node:alpine already carries a non-root "node" user; the board's own files
 # are copied in as root above, so they need handing over before this drops
 # privilege.
@@ -669,8 +675,8 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 # of minutes rather than a cold toolchain build.
 #
 # Two stages, not three: unlike the official image, this does not prune down
-# to Next's own standalone output. The migrate role below runs \`community
-# migrate\`, and \`community\` materializes @meith/cli's sources and runs them
+# to Next's own standalone output. The migrate role below runs \`meith
+# migrate\`, and \`meith\` materializes @meith/cli's sources and runs them
 # with tsx at the moment it runs (see the meith repository's
 # docs/contributing/development.md, "Consuming the board from a workspace") — it needs
 # the full, un-pruned node_modules tree this board installed, not what Next
@@ -712,6 +718,23 @@ ENV PORT=3000
 ENV HOSTNAME=0.0.0.0
 EXPOSE 3000
 
+# Uploaded files — avatars, board images, attachments — land here, and the
+# compose file mounts the persistent "uploads" volume over this path. Creating
+# it in the image, owned by node, is what lets the fresh volume inherit that
+# ownership; UPLOADS_DIR gives the board an absolute path so the working
+# directory never decides where uploads go. Without both, uploads land on the
+# container's own layer and a redeploy discards them.
+ENV UPLOADS_DIR=/app/.uploads
+RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
+
+# \`meith <command>\` on PATH runs this board's own operator CLI — the same one
+# node_modules/.bin/meith is — so a Coolify terminal or \`docker compose exec web
+# meith ...\` needs no path. It cd's to /board so the CLI finds this board's
+# config, and overrides any wrapper an inherited base image installed, which
+# would target the board that image was built from, not this one.
+RUN printf '#!/bin/sh\\ncd /board\\nexec node_modules/.bin/meith "$@"\\n' > /usr/local/bin/meith \\
+  && chmod +x /usr/local/bin/meith
+
 # node:alpine already carries a non-root "node" user; the board's own files
 # are copied in as root above, so they need handing over before this drops
 # privilege.
@@ -741,22 +764,22 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 set -e
 
 # An explicit command wins over the role, the same as the official image —
-# \`docker run <image> node_modules/.bin/community --help\` should still run
-# the CLI rather than silently starting the web server.
+# \`docker compose run --rm web meith --help\` (or \`exec\` into the running
+# container) should run the CLI rather than silently starting the web server.
 if [ "$#" -gt 0 ]; then
   exec "$@"
 fi
 
-case "\${COMMUNITY_ROLE:-web}" in
+case "\${MEITH_ROLE:-web}" in
   migrate)
     # Runs to completion and exits; compose's one-shot service waits on it.
-    exec node_modules/.bin/community migrate
+    exec node_modules/.bin/meith migrate
     ;;
   web)
     exec node_modules/.bin/forum-web start
     ;;
   *)
-    echo "Unknown COMMUNITY_ROLE: \${COMMUNITY_ROLE}. Expected 'web' or 'migrate'." >&2
+    echo "Unknown MEITH_ROLE: \${MEITH_ROLE}. Expected 'web' or 'migrate'." >&2
     exit 1
     ;;
 esac
@@ -771,7 +794,7 @@ esac
 # a health probe taken while it runs has no opinion.
 set -e
 
-if [ "\${COMMUNITY_ROLE:-web}" = "migrate" ]; then
+if [ "\${MEITH_ROLE:-web}" = "migrate" ]; then
   exit 0
 fi
 
@@ -911,7 +934,7 @@ services:
     build: .
     image: ${name}
     environment:
-      COMMUNITY_ROLE: migrate
+      MEITH_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
@@ -1044,7 +1067,7 @@ services:
     # runs the old code.
     pull_policy: always
     environment:
-      COMMUNITY_ROLE: migrate
+      MEITH_ROLE: migrate
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
@@ -1244,7 +1267,7 @@ Two things nothing configures for you, on either path:
   loop calling \`/api/system/tick\` once a minute, since \`@meith/web\`'s own
   worker package is not something a board outside the meith monorepo can
   depend on yet. Deploy some other way and something still has to call that
-  route (or run \`community task:run\`) every minute, or nothing catches up
+  route (or run \`meith task:run\`) every minute, or nothing catches up
   and nothing errors.
 
 ## Local
@@ -1262,8 +1285,8 @@ Posting needs Postgres. Copy \`.env.example\` to \`.env.local\`, set
 \`DATABASE_URL\` and the two secrets in it, then:
 
 \`\`\`sh
-npm run community -- migrate
-echo "<password>" | npm run community -- user:create --username <name> --email <address> --group administrators
+npm run meith -- migrate
+echo "<password>" | npm run meith -- user:create --username <name> --email <address> --group administrators
 \`\`\`
 
 ## Configuring
@@ -1274,9 +1297,43 @@ echo "<password>" | npm run community -- user:create --username <name> --email <
 - **\`/admin\`** — settings, forums, groups, members, themes, maintenance. An
   administrator re-enters their password to get in, and again for anything
   destructive.
-- **\`npm run community -- --help\`** — the operator CLI. Everything the panel does
+- **\`npm run meith -- --help\`** — the operator CLI. Everything the panel does
   and a few things it cannot, without a browser.
 
+## Installing plugins and themes
+
+Nothing installs into a running container — a plugin or theme has to be
+built into the image. In this repository:
+
+1. **Add it.** A **plugin** is one command, which installs the package and
+   registers it:
+
+   \`\`\`sh
+   npm run meith -- plugin:add @meith/plugin-dues
+   \`\`\`
+
+   It writes \`board.plugins.json\` and regenerates \`meith.plugins.ts\` for you
+   (\`npm run meith -- plugin:remove <key>\` reverses it). A **theme** is
+   \`npm install --save-exact @meith/theme-midnight\`, then an entry in
+   \`meith.config.ts\`'s \`themes\` map following the shape of the \`default\` one
+   already there — set \`defaultTheme\` to its key to make it the board's
+   default.
+
+2. **Commit and push**, then **Redeploy** from Coolify — pushing alone does
+   not rebuild. Quick start builds the new image on that redeploy; advanced/prebuilt
+   waits for \`.github/workflows/build.yml\` to finish first, and Redeploy is
+   what actually pulls the result.
+
+3. **If it ships database changes, apply them once it is up** — from
+   **Admin → System** (**Version & migrations**) in the browser, or:
+
+   \`\`\`sh
+   docker compose run --rm web meith upgrade
+   \`\`\`
+
+See [Installing plugins and themes](${repositoryUrl}/blob/main/docs/customization/installing.md)
+for the full guide.
+
 ## Upgrading
 
 \`\`\`sh
@@ -1317,7 +1374,7 @@ project's own \`.npmrc\` sets \`save-exact=true\` for the same reason, so an
 \`npm install\` of anything else here — a plugin, say — stays pinned too; the
 build workflow also refuses to build from anything but an exact version, as
 a second line of defense. Once the rebuilt image is deployed, run
-\`npm run community -- upgrade\` against it for the plugin migrations — see
+\`npm run meith -- upgrade\` against it for the plugin migrations — see
 [the operator CLI](${repositoryUrl}/blob/main/docs/guides/operations/operating.md#the-operator-cli)
 for running it against this deployment.
 
@@ -1577,9 +1634,9 @@ A board must stay movable, and the Blob store is the one part of this shape that
 is not portable: Neon and Upstash hand out ordinary Postgres and Redis strings
 that any host accepts, but a Vercel Blob store is reachable only through Vercel's
 own API and there is no bucket to sync out of it. **The uploads are the thing you
-have to carry out deliberately, and \`community backup\` is how.**
+have to carry out deliberately, and \`meith backup\` is how.**
 
-Under \`FILESTORE_DRIVER=blob\`, \`community backup\` includes the uploads **by
+Under \`FILESTORE_DRIVER=blob\`, \`meith backup\` includes the uploads **by
 default** — it walks the Blob store, pulls every object, and puts them in the
 bundle beside the database dump. This is the opposite of the \`s3\` default, which
 skips them, because a bucket has its own backup story you can drive yourself and
@@ -1590,7 +1647,7 @@ DATABASE_URL=…            # Neon's pooled string
 DIRECT_DATABASE_URL=…     # Neon's DATABASE_URL_UNPOOLED
 FILESTORE_DRIVER=blob
 BLOB_READ_WRITE_TOKEN=…   # create one on the store; see below
-npm run community -- backup
+npm run meith -- backup
 \`\`\`
 
 Run that from a checkout of this repository, with those four values in the
@@ -1611,10 +1668,10 @@ so the same bundle moves the board either onward or away:
 
 \`\`\`sh
 # onto a self-hosted board with a bucket
-FILESTORE_DRIVER=s3 S3_BUCKET=… RESTORE_DATABASE_URL=… npm run community -- restore bundle.tar.gz
+FILESTORE_DRIVER=s3 S3_BUCKET=… RESTORE_DATABASE_URL=… npm run meith -- restore bundle.tar.gz
 
 # onto a board that keeps uploads on its own disk
-RESTORE_DATABASE_URL=… npm run community -- restore bundle.tar.gz --uploads-dir ./uploads
+RESTORE_DATABASE_URL=… npm run meith -- restore bundle.tar.gz --uploads-dir ./uploads
 \`\`\`
 
 Take one before you need it. A Blob store deleted with the Vercel project takes