create-snagset 0.1.16 → 0.1.18

package/README.md

@@ -82,5 +82,7 @@ line: expect the odd rough edge, and pin the version if you need stability.
 Issues and notes are welcome at
 [snagset/snagset](https://github.com/snagset/snagset).
 
-AGPL-3.0-only. The widget you put on a client's site is
-[`snagset`](https://www.npmjs.com/package/snagset), and it is MIT.
+MIT — the folder it writes is yours. The server it installs,
+[`@snagset/server`](https://www.npmjs.com/package/@snagset/server), is
+AGPL-3.0-only; the widget you put on a client's site,
+[`snagset`](https://www.npmjs.com/package/snagset), is MIT.

package/dist/scaffold.js

@@ -3,7 +3,7 @@ import { basename, dirname, join, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import { randomBytes } from "node:crypto";
 /**
- * `npx create-snagset` — D63's self-host, the `create-next-app` model.
+ * `npx create-snagset` — the self-host, the `create-next-app` model.
  *
  * ── WHY A SCAFFOLDER AND NOT `git clone` ──
  *
@@ -116,7 +116,7 @@ export function scaffold(target, cwd = process.cwd()) {
      * The alternative — ship an example and tell them to copy it — adds a step
      * between the scaffold and the first run, which is the step where an install
      * stalls. And generating the key here rather than letting the server do it
-     * on first boot matters for the deploy case: 08 §4.2's generate-to-disk is
+     * on first boot matters for the deploy case: The generate-to-disk is
      * bin-only, so an operator who scaffolds locally and deploys to a platform
      * would otherwise discover on the far side that they had no key to set.
      */

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "create-snagset",
-  "version": "0.1.16",
+  "version": "0.1.18",
   "private": false,
   "type": "module",
   "description": "Scaffold your own Snagset instance. One command, Postgres included, one variable to fill in.",
-  "license": "AGPL-3.0-only",
+  "license": "MIT",
   "bin": {
     "create-snagset": "dist/index.js"
   },