create-meith 0.33.4 → 0.34.0

package/dist/bin.mjs

@@ -136,7 +136,14 @@ var ENV_BACKUP_BLOCK = `# The off-site backup destination: an S3-compatible buck
 # BACKUP_S3_ACCESS_KEY_ID=
 # BACKUP_S3_SECRET_ACCESS_KEY=
 # BACKUP_S3_ENDPOINT=
-# BACKUP_S3_PREFIX=`;
+# BACKUP_S3_PREFIX=
+#
+# Or a WebDAV folder instead of a bucket \u2014 Nextcloud, ownCloud, a Hetzner
+# Storage Box. The address of a folder that already exists; username and
+# password together or not at all. One destination or the other, never both.
+# BACKUP_WEBDAV_URL=
+# BACKUP_WEBDAV_USERNAME=
+# BACKUP_WEBDAV_PASSWORD=`;
 function selfHostEnvExample(name) {
   return `# ${name} \u2014 environment.
 #
@@ -682,6 +689,14 @@ EXPOSE 3000
 ENV UPLOADS_DIR=/app/.uploads
 RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
 
+# The ring of backup bundles the admin panel's Backups screen writes, lists
+# and prunes, and the postgres client tools \`meith backup\` and the panel's
+# backups dump with. The compose file mounts the persistent "backups" volume
+# over this path.
+RUN apk add --no-cache postgresql18-client
+ENV BACKUP_DIR=/backups
+RUN mkdir -p /backups && chown node:node /backups
+
 # \`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
@@ -776,6 +791,14 @@ EXPOSE 3000
 ENV UPLOADS_DIR=/app/.uploads
 RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
 
+# The ring of backup bundles the admin panel's Backups screen writes, lists
+# and prunes, and the postgres client tools \`meith backup\` and the panel's
+# backups dump with. The compose file mounts the persistent "backups" volume
+# over this path.
+RUN apk add --no-cache postgresql18-client
+ENV BACKUP_DIR=/backups
+RUN mkdir -p /backups && chown node:node /backups
+
 # \`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
@@ -982,6 +1005,25 @@ services:
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
+      FILESTORE_DRIVER: local
+      # So that "back up before migrating" (a board setting) can ship the
+      # bundle it takes to the same off-site destination the web container
+      # uses. Unset until the four required values are filled in on the
+      # Coolify resource.
+      BACKUP_S3_BUCKET: \${BACKUP_S3_BUCKET:-}
+      BACKUP_S3_REGION: \${BACKUP_S3_REGION:-}
+      BACKUP_S3_ACCESS_KEY_ID: \${BACKUP_S3_ACCESS_KEY_ID:-}
+      BACKUP_S3_SECRET_ACCESS_KEY: \${BACKUP_S3_SECRET_ACCESS_KEY:-}
+      BACKUP_S3_ENDPOINT: \${BACKUP_S3_ENDPOINT:-}
+      BACKUP_S3_PREFIX: \${BACKUP_S3_PREFIX:-}
+      BACKUP_WEBDAV_URL: \${BACKUP_WEBDAV_URL:-}
+      BACKUP_WEBDAV_USERNAME: \${BACKUP_WEBDAV_USERNAME:-}
+      BACKUP_WEBDAV_PASSWORD: \${BACKUP_WEBDAV_PASSWORD:-}
+    volumes:
+      # Both volumes, so that the bundle "back up before migrating" writes
+      # carries the uploads and lands in the same ring as every other backup.
+      - uploads:/app/.uploads
+      - backups:/backups
     depends_on:
       postgres:
         condition: service_healthy
@@ -1036,11 +1078,15 @@ services:
       - BACKUP_S3_SECRET_ACCESS_KEY=\${BACKUP_S3_SECRET_ACCESS_KEY:-}
       - BACKUP_S3_ENDPOINT=\${BACKUP_S3_ENDPOINT:-}
       - BACKUP_S3_PREFIX=\${BACKUP_S3_PREFIX:-}
+      - BACKUP_WEBDAV_URL=\${BACKUP_WEBDAV_URL:-}
+      - BACKUP_WEBDAV_USERNAME=\${BACKUP_WEBDAV_USERNAME:-}
+      - BACKUP_WEBDAV_PASSWORD=\${BACKUP_WEBDAV_PASSWORD:-}
     volumes:
       - uploads:/app/.uploads
-      # Where \`meith backup --dir /backups\` writes its ring of bundles. A
-      # named volume rather than the container filesystem, so the ring survives
-      # every redeploy.
+      # The ring of backup bundles: what the admin panel's Backups screen
+      # writes, lists and downloads, and what \`meith backup --dir /backups\`
+      # writes. A named volume rather than the container filesystem, so the
+      # ring survives every redeploy.
       - backups:/backups
     depends_on:
       postgres:
@@ -1131,6 +1177,25 @@ services:
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
+      FILESTORE_DRIVER: local
+      # So that "back up before migrating" (a board setting) can ship the
+      # bundle it takes to the same off-site destination the web container
+      # uses. Unset until the four required values are filled in on the
+      # Coolify resource.
+      BACKUP_S3_BUCKET: \${BACKUP_S3_BUCKET:-}
+      BACKUP_S3_REGION: \${BACKUP_S3_REGION:-}
+      BACKUP_S3_ACCESS_KEY_ID: \${BACKUP_S3_ACCESS_KEY_ID:-}
+      BACKUP_S3_SECRET_ACCESS_KEY: \${BACKUP_S3_SECRET_ACCESS_KEY:-}
+      BACKUP_S3_ENDPOINT: \${BACKUP_S3_ENDPOINT:-}
+      BACKUP_S3_PREFIX: \${BACKUP_S3_PREFIX:-}
+      BACKUP_WEBDAV_URL: \${BACKUP_WEBDAV_URL:-}
+      BACKUP_WEBDAV_USERNAME: \${BACKUP_WEBDAV_USERNAME:-}
+      BACKUP_WEBDAV_PASSWORD: \${BACKUP_WEBDAV_PASSWORD:-}
+    volumes:
+      # Both volumes, so that the bundle "back up before migrating" writes
+      # carries the uploads and lands in the same ring as every other backup.
+      - uploads:/app/.uploads
+      - backups:/backups
     depends_on:
       postgres:
         condition: service_healthy
@@ -1185,11 +1250,15 @@ services:
       - BACKUP_S3_SECRET_ACCESS_KEY=\${BACKUP_S3_SECRET_ACCESS_KEY:-}
       - BACKUP_S3_ENDPOINT=\${BACKUP_S3_ENDPOINT:-}
       - BACKUP_S3_PREFIX=\${BACKUP_S3_PREFIX:-}
+      - BACKUP_WEBDAV_URL=\${BACKUP_WEBDAV_URL:-}
+      - BACKUP_WEBDAV_USERNAME=\${BACKUP_WEBDAV_USERNAME:-}
+      - BACKUP_WEBDAV_PASSWORD=\${BACKUP_WEBDAV_PASSWORD:-}
     volumes:
       - uploads:/app/.uploads
-      # Where \`meith backup --dir /backups\` writes its ring of bundles. A
-      # named volume rather than the container filesystem, so the ring survives
-      # every redeploy.
+      # The ring of backup bundles: what the admin panel's Backups screen
+      # writes, lists and downloads, and what \`meith backup --dir /backups\`
+      # writes. A named volume rather than the container filesystem, so the
+      # ring survives every redeploy.
       - backups:/backups
     depends_on:
       postgres:
@@ -2760,7 +2829,7 @@ async function run(argv, version, updateOptions = {}) {
 }
 
 // src/bin.ts
-var result = await run(process.argv.slice(2), "0.33.4");
+var result = await run(process.argv.slice(2), "0.34.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.33.4",
+  "version": "0.34.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.33.4')
+const result = await run(process.argv.slice(2), '0.34.0')
 for (const line of result.lines) {
   if (result.code === 0) console.log(line)
   else console.error(line)

package/src/scaffold.ts

@@ -160,7 +160,14 @@ const ENV_BACKUP_BLOCK = `# The off-site backup destination: an S3-compatible bu
 # BACKUP_S3_ACCESS_KEY_ID=
 # BACKUP_S3_SECRET_ACCESS_KEY=
 # BACKUP_S3_ENDPOINT=
-# BACKUP_S3_PREFIX=`
+# BACKUP_S3_PREFIX=
+#
+# Or a WebDAV folder instead of a bucket — Nextcloud, ownCloud, a Hetzner
+# Storage Box. The address of a folder that already exists; username and
+# password together or not at all. One destination or the other, never both.
+# BACKUP_WEBDAV_URL=
+# BACKUP_WEBDAV_USERNAME=
+# BACKUP_WEBDAV_PASSWORD=`
 
 function selfHostEnvExample(name: string): string {
   return `# ${name} — environment.
@@ -724,6 +731,14 @@ EXPOSE 3000
 ENV UPLOADS_DIR=/app/.uploads
 RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
 
+# The ring of backup bundles the admin panel's Backups screen writes, lists
+# and prunes, and the postgres client tools \`meith backup\` and the panel's
+# backups dump with. The compose file mounts the persistent "backups" volume
+# over this path.
+RUN apk add --no-cache postgresql18-client
+ENV BACKUP_DIR=/backups
+RUN mkdir -p /backups && chown node:node /backups
+
 # \`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
@@ -819,6 +834,14 @@ EXPOSE 3000
 ENV UPLOADS_DIR=/app/.uploads
 RUN mkdir -p /app/.uploads && chown node:node /app/.uploads
 
+# The ring of backup bundles the admin panel's Backups screen writes, lists
+# and prunes, and the postgres client tools \`meith backup\` and the panel's
+# backups dump with. The compose file mounts the persistent "backups" volume
+# over this path.
+RUN apk add --no-cache postgresql18-client
+ENV BACKUP_DIR=/backups
+RUN mkdir -p /backups && chown node:node /backups
+
 # \`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
@@ -1030,6 +1053,25 @@ services:
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
+      FILESTORE_DRIVER: local
+      # So that "back up before migrating" (a board setting) can ship the
+      # bundle it takes to the same off-site destination the web container
+      # uses. Unset until the four required values are filled in on the
+      # Coolify resource.
+      BACKUP_S3_BUCKET: \${BACKUP_S3_BUCKET:-}
+      BACKUP_S3_REGION: \${BACKUP_S3_REGION:-}
+      BACKUP_S3_ACCESS_KEY_ID: \${BACKUP_S3_ACCESS_KEY_ID:-}
+      BACKUP_S3_SECRET_ACCESS_KEY: \${BACKUP_S3_SECRET_ACCESS_KEY:-}
+      BACKUP_S3_ENDPOINT: \${BACKUP_S3_ENDPOINT:-}
+      BACKUP_S3_PREFIX: \${BACKUP_S3_PREFIX:-}
+      BACKUP_WEBDAV_URL: \${BACKUP_WEBDAV_URL:-}
+      BACKUP_WEBDAV_USERNAME: \${BACKUP_WEBDAV_USERNAME:-}
+      BACKUP_WEBDAV_PASSWORD: \${BACKUP_WEBDAV_PASSWORD:-}
+    volumes:
+      # Both volumes, so that the bundle "back up before migrating" writes
+      # carries the uploads and lands in the same ring as every other backup.
+      - uploads:/app/.uploads
+      - backups:/backups
     depends_on:
       postgres:
         condition: service_healthy
@@ -1084,11 +1126,15 @@ services:
       - BACKUP_S3_SECRET_ACCESS_KEY=\${BACKUP_S3_SECRET_ACCESS_KEY:-}
       - BACKUP_S3_ENDPOINT=\${BACKUP_S3_ENDPOINT:-}
       - BACKUP_S3_PREFIX=\${BACKUP_S3_PREFIX:-}
+      - BACKUP_WEBDAV_URL=\${BACKUP_WEBDAV_URL:-}
+      - BACKUP_WEBDAV_USERNAME=\${BACKUP_WEBDAV_USERNAME:-}
+      - BACKUP_WEBDAV_PASSWORD=\${BACKUP_WEBDAV_PASSWORD:-}
     volumes:
       - uploads:/app/.uploads
-      # Where \`meith backup --dir /backups\` writes its ring of bundles. A
-      # named volume rather than the container filesystem, so the ring survives
-      # every redeploy.
+      # The ring of backup bundles: what the admin panel's Backups screen
+      # writes, lists and downloads, and what \`meith backup --dir /backups\`
+      # writes. A named volume rather than the container filesystem, so the
+      # ring survives every redeploy.
       - backups:/backups
     depends_on:
       postgres:
@@ -1180,6 +1226,25 @@ services:
       DATABASE_URL: postgres://community:$SERVICE_PASSWORD_POSTGRES@postgres:5432/community
       AUTH_SECRET: $SERVICE_BASE64_64_AUTH
       TICK_SECRET: $SERVICE_BASE64_64_TICK
+      FILESTORE_DRIVER: local
+      # So that "back up before migrating" (a board setting) can ship the
+      # bundle it takes to the same off-site destination the web container
+      # uses. Unset until the four required values are filled in on the
+      # Coolify resource.
+      BACKUP_S3_BUCKET: \${BACKUP_S3_BUCKET:-}
+      BACKUP_S3_REGION: \${BACKUP_S3_REGION:-}
+      BACKUP_S3_ACCESS_KEY_ID: \${BACKUP_S3_ACCESS_KEY_ID:-}
+      BACKUP_S3_SECRET_ACCESS_KEY: \${BACKUP_S3_SECRET_ACCESS_KEY:-}
+      BACKUP_S3_ENDPOINT: \${BACKUP_S3_ENDPOINT:-}
+      BACKUP_S3_PREFIX: \${BACKUP_S3_PREFIX:-}
+      BACKUP_WEBDAV_URL: \${BACKUP_WEBDAV_URL:-}
+      BACKUP_WEBDAV_USERNAME: \${BACKUP_WEBDAV_USERNAME:-}
+      BACKUP_WEBDAV_PASSWORD: \${BACKUP_WEBDAV_PASSWORD:-}
+    volumes:
+      # Both volumes, so that the bundle "back up before migrating" writes
+      # carries the uploads and lands in the same ring as every other backup.
+      - uploads:/app/.uploads
+      - backups:/backups
     depends_on:
       postgres:
         condition: service_healthy
@@ -1234,11 +1299,15 @@ services:
       - BACKUP_S3_SECRET_ACCESS_KEY=\${BACKUP_S3_SECRET_ACCESS_KEY:-}
       - BACKUP_S3_ENDPOINT=\${BACKUP_S3_ENDPOINT:-}
       - BACKUP_S3_PREFIX=\${BACKUP_S3_PREFIX:-}
+      - BACKUP_WEBDAV_URL=\${BACKUP_WEBDAV_URL:-}
+      - BACKUP_WEBDAV_USERNAME=\${BACKUP_WEBDAV_USERNAME:-}
+      - BACKUP_WEBDAV_PASSWORD=\${BACKUP_WEBDAV_PASSWORD:-}
     volumes:
       - uploads:/app/.uploads
-      # Where \`meith backup --dir /backups\` writes its ring of bundles. A
-      # named volume rather than the container filesystem, so the ring survives
-      # every redeploy.
+      # The ring of backup bundles: what the admin panel's Backups screen
+      # writes, lists and downloads, and what \`meith backup --dir /backups\`
+      # writes. A named volume rather than the container filesystem, so the
+      # ring survives every redeploy.
       - backups:/backups
     depends_on:
       postgres: