create-meith 0.23.0 → 0.23.2

package/dist/bin.mjs

@@ -325,7 +325,7 @@ var SELF_HOST_DEPLOY_KIT = [
   ".dockerignore",
   ".github/workflows/build.yml",
   "Dockerfile",
-  "docker-compose.yml",
+  "docker-compose.yaml",
   "docker-entrypoint.sh",
   "docker-healthcheck.sh"
 ];
@@ -534,7 +534,7 @@ export function installedPluginDefinitions() {
 # 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
 # traced as reachable from the web server alone. The tick itself is driven
-# by docker-compose.yml's own \`worker\` service \u2014 a lightweight loop against
+# by docker-compose.yaml's own \`worker\` service \u2014 a lightweight loop against
 # /api/system/tick, not a compiled worker process, because @meith/worker is
 # not published (see the meith repository's docs/contributing/release.md).
 ARG MEITH_VERSION
@@ -593,7 +593,7 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 #
 # "web" (the default) runs the board; "migrate" applies the schema and
 # exits. There is no "worker" role in this image: @meith/worker is not
-# published, so nothing here can run it \u2014 docker-compose.yml's own \`worker\`
+# published, so nothing here can run it \u2014 docker-compose.yaml's own \`worker\`
 # service drives the tick a different way, calling this image's web role
 # over HTTP instead of running as a role of this image.
 set -e
@@ -699,27 +699,33 @@ jobs:
           {
             echo "## Deploy this image"
             echo
-            echo "Paste this into the MEITH_IMAGE variable on the Coolify resource:"
+            echo "Either of these goes in the MEITH_IMAGE variable on the Coolify"
+            echo "resource:"
             echo
             echo "    $IMAGE:\${{ github.sha }}"
             echo
-            echo "This tag names this run's build and nothing else, ever. $IMAGE:latest"
-            echo "also pushed, as a convenience for a quick manual pull; it moves on"
-            echo "every push to main, so any later Coolify redeploy \u2014 for any reason,"
-            echo "not necessarily this one \u2014 pulls whatever main most recently built,"
-            echo "including a commit still mid-feature. Prefer the sha above for the"
-            echo "value you actually set on the resource."
+            echo "    $IMAGE:latest"
             echo
-            echo "## One-time: make the package public"
+            echo "The first names this run's build and nothing else, ever: nothing"
+            echo "moves under you, and an upgrade is you editing this variable."
             echo
-            echo "This package starts private. Coolify's pull fails until you visit"
-            echo "$PKG_URL and change its visibility \u2014 **Package settings** \u2192"
-            echo "**Change visibility** \u2192 **Public**."
+            echo "The second follows main \u2014 every push rebuilds it and Coolify's next"
+            echo "Redeploy picks that build up, a commit still mid-feature included."
+            echo "That is the trade the quickstart takes while a board is young and"
+            echo "still gaining plugins: installing one is a push and a Redeploy, with"
+            echo "nothing on the resource to edit."
+            echo
+            echo "## One-time: check the package is public"
+            echo
+            echo "Coolify can only pull a public package, and this one may already be"
+            echo "one \u2014 a build from a public repository usually lands public. Open"
+            echo "$PKG_URL: if it does not already say Public, change it there \u2014"
+            echo "**Package settings** \u2192 **Change visibility** \u2192 **Public**."
           } >> "$GITHUB_STEP_SUMMARY"
 `
   );
   files.set(
-    "docker-compose.yml",
+    "docker-compose.yaml",
     `# ${name}, deployed by Coolify \u2014 the same shape as the meith repository's own
 # docker/compose.coolify.yml: db, migrate, web, worker. See README.md for
 # the three-step deploy story this file is the last step of.
@@ -837,7 +843,7 @@ A forum, built on [Meith](${repositoryUrl}).
 ## Deploy
 
 Nothing here builds on your own server \u2014 a 2 GB VPS OOMs on a Next.js build,
-which is the whole reason \`Dockerfile\`, \`docker-compose.yml\` and
+which is the whole reason \`Dockerfile\`, \`docker-compose.yaml\` and
 \`.github/workflows/build.yml\` exist: something else builds the image, the
 server only ever pulls one. Three steps, nothing to configure by hand beyond
 one value only you know:
@@ -848,25 +854,28 @@ one value only you know:
    \`GITHUB_TOKEN\` every GitHub Actions run already carries. No secret to
    add, no registry account beyond the GitHub account you already have.
 
-   Open the run under the repository's **Actions** tab once it finishes \u2014
-   its **Summary** prints the two things left: the exact image to paste
-   into step 2 below, and a direct link to the one-time step of making the
-   package public. It starts **private**, and Coolify's pull fails with an
-   authentication error no operator can act on until that is done.
-
-2. **Point [Coolify](https://coolify.io) at \`docker-compose.yml\`** \u2014 a Docker
-   Compose resource, this repository as its source. \`docker-compose.yml\` already
-   carries Coolify's own "magic variables" for \`AUTH_SECRET\`,
-   \`TICK_SECRET\` and the database password, generated on the first deploy
-   and never typed in. The one thing Coolify cannot generate is the image
-   step 1 just pushed: set \`MEITH_IMAGE\` in the resource's own environment
-   to the value that run's Summary printed \u2014 \`ghcr.io/<you>/${name}:\${{ github.sha }}\`,
-   a pin that only ever names that one build (\`docker-compose.yml\` refuses
-   to start without this set, with a message saying why). The same run also
-   pushes \`ghcr.io/<you>/${name}:latest\` as a convenience for a quick manual
-   pull, but it moves on every push to \`main\` \u2014 set it on the resource and a
-   later, unrelated redeploy can pull whatever \`main\` most recently built,
-   commit still mid-feature included.
+   That build is the thing step 2 waits on: open the repository's
+   **Actions** tab and let the run finish, because its **Summary** is where
+   the exact image to paste into step 2 comes from. The Summary also links
+   the package itself, to check it is public \u2014 a build from a public
+   repository usually lands public already, and a private one fails
+   Coolify's pull with an authentication error no operator can act on.
+
+2. **Point [Coolify](https://coolify.io) at \`docker-compose.yaml\`** \u2014 a
+   **Public Git repository** resource with **Docker Compose** as its build
+   pack, this repository as its source. The name is Coolify's own default,
+   so its **Compose file** field is already right when the form opens, and
+   the file already carries Coolify's own "magic variables" for
+   \`AUTH_SECRET\`, \`TICK_SECRET\` and the database password, generated on
+   the first deploy and never typed in. The one thing Coolify cannot
+   generate is the image step 1 just pushed: set \`MEITH_IMAGE\` in the
+   resource's own environment to one of the two values that run's Summary
+   printed (\`docker-compose.yaml\` refuses to start without it, with a
+   message saying why). \`ghcr.io/<you>/${name}:\${{ github.sha }}\` names
+   that one build and nothing else, ever; \`ghcr.io/<you>/${name}:latest\`
+   follows \`main\` instead, so installing a plugin later is a push and a
+   **Redeploy** \u2014 the trade the quickstart takes, at the cost of an
+   unrelated redeploy pulling whatever \`main\` most recently built.
 
 3. **Deploy, then \`/install\` on your own domain.** Coolify issues the
    certificate; the installer from there is the one
@@ -882,7 +891,7 @@ build side of this, for a board of any size.
 
 **Building it yourself**: works on any machine with Docker, if you would
 rather not use GitHub Actions for the build \u2014 push the result wherever
-\`docker-compose.yml\`'s \`MEITH_IMAGE\` can reach.
+\`docker-compose.yaml\`'s \`MEITH_IMAGE\` can reach.
 
 \`\`\`sh
 docker build --build-arg MEITH_VERSION=$(node -p "require('./package.json').dependencies['@meith/web']") -t ${name} .
@@ -890,14 +899,14 @@ docker build --build-arg MEITH_VERSION=$(node -p "require('./package.json').depe
 
 **Without a panel**: [docs/getting-started/deployment/docker-compose.md](${repositoryUrl}/blob/main/docs/getting-started/deployment/docker-compose.md)
 is the same four containers by hand \u2014 your own \`.env\`, a reverse proxy you
-already run, no Coolify. \`Dockerfile\` and \`docker-compose.yml\` here are this
+already run, no Coolify. \`Dockerfile\` and \`docker-compose.yaml\` here are this
 board's own version of exactly that shape.
 
 Two things nothing configures for you:
 
 - **Mail.** Until \`MAIL_DRIVER\` and its three settings exist, every message is
   written to the log and delivered to nobody, so password reset fails silently.
-- **The tick.** \`docker-compose.yml\`'s \`worker\` service drives it here \u2014 a small
+- **The tick.** \`docker-compose.yaml\`'s \`worker\` service drives it here \u2014 a small
   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
@@ -1856,7 +1865,7 @@ async function run(argv, version) {
 }
 
 // src/bin.ts
-var result = await run(process.argv.slice(2), "0.23.0");
+var result = await run(process.argv.slice(2), "0.23.2");
 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.23.0",
+  "version": "0.23.2",
   "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.23.0')
+const result = await run(process.argv.slice(2), '0.23.2')
 for (const line of result.lines) {
   if (result.code === 0) console.log(line)
   else console.error(line)

package/src/scaffold.ts

@@ -352,7 +352,7 @@ const SELF_HOST_DEPLOY_KIT = [
   '.dockerignore',
   '.github/workflows/build.yml',
   'Dockerfile',
-  'docker-compose.yml',
+  'docker-compose.yaml',
   'docker-entrypoint.sh',
   'docker-healthcheck.sh',
 ] as const
@@ -573,7 +573,7 @@ export function installedPluginDefinitions() {
 # 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
 # traced as reachable from the web server alone. The tick itself is driven
-# by docker-compose.yml's own \`worker\` service — a lightweight loop against
+# by docker-compose.yaml's own \`worker\` service — a lightweight loop against
 # /api/system/tick, not a compiled worker process, because @meith/worker is
 # not published (see the meith repository's docs/contributing/release.md).
 ARG MEITH_VERSION
@@ -633,7 +633,7 @@ ENTRYPOINT ["./docker-entrypoint.sh"]
 #
 # "web" (the default) runs the board; "migrate" applies the schema and
 # exits. There is no "worker" role in this image: @meith/worker is not
-# published, so nothing here can run it — docker-compose.yml's own \`worker\`
+# published, so nothing here can run it — docker-compose.yaml's own \`worker\`
 # service drives the tick a different way, calling this image's web role
 # over HTTP instead of running as a role of this image.
 set -e
@@ -742,28 +742,34 @@ jobs:
           {
             echo "## Deploy this image"
             echo
-            echo "Paste this into the MEITH_IMAGE variable on the Coolify resource:"
+            echo "Either of these goes in the MEITH_IMAGE variable on the Coolify"
+            echo "resource:"
             echo
             echo "    $IMAGE:\${{ github.sha }}"
             echo
-            echo "This tag names this run's build and nothing else, ever. $IMAGE:latest"
-            echo "also pushed, as a convenience for a quick manual pull; it moves on"
-            echo "every push to main, so any later Coolify redeploy — for any reason,"
-            echo "not necessarily this one — pulls whatever main most recently built,"
-            echo "including a commit still mid-feature. Prefer the sha above for the"
-            echo "value you actually set on the resource."
+            echo "    $IMAGE:latest"
             echo
-            echo "## One-time: make the package public"
+            echo "The first names this run's build and nothing else, ever: nothing"
+            echo "moves under you, and an upgrade is you editing this variable."
             echo
-            echo "This package starts private. Coolify's pull fails until you visit"
-            echo "$PKG_URL and change its visibility — **Package settings** →"
-            echo "**Change visibility** → **Public**."
+            echo "The second follows main — every push rebuilds it and Coolify's next"
+            echo "Redeploy picks that build up, a commit still mid-feature included."
+            echo "That is the trade the quickstart takes while a board is young and"
+            echo "still gaining plugins: installing one is a push and a Redeploy, with"
+            echo "nothing on the resource to edit."
+            echo
+            echo "## One-time: check the package is public"
+            echo
+            echo "Coolify can only pull a public package, and this one may already be"
+            echo "one — a build from a public repository usually lands public. Open"
+            echo "$PKG_URL: if it does not already say Public, change it there —"
+            echo "**Package settings** → **Change visibility** → **Public**."
           } >> "$GITHUB_STEP_SUMMARY"
 `,
   )
 
   files.set(
-    'docker-compose.yml',
+    'docker-compose.yaml',
     `# ${name}, deployed by Coolify — the same shape as the meith repository's own
 # docker/compose.coolify.yml: db, migrate, web, worker. See README.md for
 # the three-step deploy story this file is the last step of.
@@ -882,7 +888,7 @@ A forum, built on [Meith](${repositoryUrl}).
 ## Deploy
 
 Nothing here builds on your own server — a 2 GB VPS OOMs on a Next.js build,
-which is the whole reason \`Dockerfile\`, \`docker-compose.yml\` and
+which is the whole reason \`Dockerfile\`, \`docker-compose.yaml\` and
 \`.github/workflows/build.yml\` exist: something else builds the image, the
 server only ever pulls one. Three steps, nothing to configure by hand beyond
 one value only you know:
@@ -893,25 +899,28 @@ one value only you know:
    \`GITHUB_TOKEN\` every GitHub Actions run already carries. No secret to
    add, no registry account beyond the GitHub account you already have.
 
-   Open the run under the repository's **Actions** tab once it finishes —
-   its **Summary** prints the two things left: the exact image to paste
-   into step 2 below, and a direct link to the one-time step of making the
-   package public. It starts **private**, and Coolify's pull fails with an
-   authentication error no operator can act on until that is done.
-
-2. **Point [Coolify](https://coolify.io) at \`docker-compose.yml\`** — a Docker
-   Compose resource, this repository as its source. \`docker-compose.yml\` already
-   carries Coolify's own "magic variables" for \`AUTH_SECRET\`,
-   \`TICK_SECRET\` and the database password, generated on the first deploy
-   and never typed in. The one thing Coolify cannot generate is the image
-   step 1 just pushed: set \`MEITH_IMAGE\` in the resource's own environment
-   to the value that run's Summary printed — \`ghcr.io/<you>/${name}:\${{ github.sha }}\`,
-   a pin that only ever names that one build (\`docker-compose.yml\` refuses
-   to start without this set, with a message saying why). The same run also
-   pushes \`ghcr.io/<you>/${name}:latest\` as a convenience for a quick manual
-   pull, but it moves on every push to \`main\` — set it on the resource and a
-   later, unrelated redeploy can pull whatever \`main\` most recently built,
-   commit still mid-feature included.
+   That build is the thing step 2 waits on: open the repository's
+   **Actions** tab and let the run finish, because its **Summary** is where
+   the exact image to paste into step 2 comes from. The Summary also links
+   the package itself, to check it is public — a build from a public
+   repository usually lands public already, and a private one fails
+   Coolify's pull with an authentication error no operator can act on.
+
+2. **Point [Coolify](https://coolify.io) at \`docker-compose.yaml\`** — a
+   **Public Git repository** resource with **Docker Compose** as its build
+   pack, this repository as its source. The name is Coolify's own default,
+   so its **Compose file** field is already right when the form opens, and
+   the file already carries Coolify's own "magic variables" for
+   \`AUTH_SECRET\`, \`TICK_SECRET\` and the database password, generated on
+   the first deploy and never typed in. The one thing Coolify cannot
+   generate is the image step 1 just pushed: set \`MEITH_IMAGE\` in the
+   resource's own environment to one of the two values that run's Summary
+   printed (\`docker-compose.yaml\` refuses to start without it, with a
+   message saying why). \`ghcr.io/<you>/${name}:\${{ github.sha }}\` names
+   that one build and nothing else, ever; \`ghcr.io/<you>/${name}:latest\`
+   follows \`main\` instead, so installing a plugin later is a push and a
+   **Redeploy** — the trade the quickstart takes, at the cost of an
+   unrelated redeploy pulling whatever \`main\` most recently built.
 
 3. **Deploy, then \`/install\` on your own domain.** Coolify issues the
    certificate; the installer from there is the one
@@ -927,7 +936,7 @@ build side of this, for a board of any size.
 
 **Building it yourself**: works on any machine with Docker, if you would
 rather not use GitHub Actions for the build — push the result wherever
-\`docker-compose.yml\`'s \`MEITH_IMAGE\` can reach.
+\`docker-compose.yaml\`'s \`MEITH_IMAGE\` can reach.
 
 \`\`\`sh
 docker build --build-arg MEITH_VERSION=$(node -p "require('./package.json').dependencies['@meith/web']") -t ${name} .
@@ -935,14 +944,14 @@ docker build --build-arg MEITH_VERSION=$(node -p "require('./package.json').depe
 
 **Without a panel**: [docs/getting-started/deployment/docker-compose.md](${repositoryUrl}/blob/main/docs/getting-started/deployment/docker-compose.md)
 is the same four containers by hand — your own \`.env\`, a reverse proxy you
-already run, no Coolify. \`Dockerfile\` and \`docker-compose.yml\` here are this
+already run, no Coolify. \`Dockerfile\` and \`docker-compose.yaml\` here are this
 board's own version of exactly that shape.
 
 Two things nothing configures for you:
 
 - **Mail.** Until \`MAIL_DRIVER\` and its three settings exist, every message is
   written to the log and delivered to nobody, so password reset fails silently.
-- **The tick.** \`docker-compose.yml\`'s \`worker\` service drives it here — a small
+- **The tick.** \`docker-compose.yaml\`'s \`worker\` service drives it here — a small
   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