create-smoodly-app 0.0.51 → 0.0.53

package/README.md

@@ -2,9 +2,9 @@
 
     npx create-smoodly-app my-site
 
-A fresh Astro or Next.js site with the Smoodly admin mounted at `/admin`, a
-Supabase project holding the schema, `.env` (Astro) or `.env.local` (Next)
-written, and a first editor who can sign in.
+A fresh Astro or Next.js site with the Smoodly admin mounted at `/admin`,
+`.env` (Astro) or `.env.local` (Next) written with a space's three values,
+the site's schema pushed to the space and the starter content seeded.
 
 ## What it asks
 
@@ -18,34 +18,23 @@ written, and a first editor who can sign in.
    gets the next-intl layout: the site under `app/[locale]/`, `i18n/`,
    `proxy.ts`, translated URLs per locale; Astro gets its own i18n config
    (`astro.config.ts` and `src/smoodly/config.ts`). Flag: `--locales en,fi`.
-4. Where content lives: a **local Supabase stack** (`supabase init` +
-   `supabase start` inside the app, with the services Smoodly never uses
-   excluded — the image proxy, edge functions, analytics, the pooler —
-   so the stack stays small beside any other you run; needs
-   the Supabase CLI and Docker; when
-   another project holds the default `543xx` ports the new one moves to the
-   next free block, `553xx` and so on, and says so) or a
-   **hosted project** (URL, publishable key, secret key; then an offer to
-   `supabase link --project-ref <ref>` + `supabase db push`, the ref taken
-   from the URL so the CLI never opens its project picker). The URL may be
-   pasted without `https://`; anything that is not an http(s) URL is refused
-   before any step runs. A custom domain has no ref, so the link is not
-   offered and the two commands are printed instead. Either way the
-   project is Smoodly's own: its tables are created unprefixed in `public`,
-   so an app that keeps its own tables in Supabase gives them a project of
-   their own, or takes Smoodly Cloud for content (DESIGN.md §1).
-5. The first editor: pick an existing Auth user or create one (email +
-   password). The `members` row is written with role `admin`, the email
-   beside the id.
-   If `@` does not appear when you type it (macOS, `@` on Option+2 with the
-   terminal's "Option as Meta" setting on), paste the address or pass
-   `--editor-email`.
+4. **Starter**: Lorem Co. (a tour of every feature, the default) or blank.
+   Flag: `--starter lorem|blank`.
+5. **The space's values**: create a project at smoodly.io, open its preview
+   space and paste the space id (`sp_…`), the secret key (`sk_…`, asked
+   hidden) and the publishable key (`pk_…`). A key of the wrong kind is
+   refused at its prompt. Flags: `--space`, `--secret-key`,
+   `--publishable-key`; a value cannot be defaulted, so `--yes` still asks,
+   and a run with no terminal and no flags names the three flags.
 
-Every prompt has a flag, so CI can run it: `--framework astro|next`, `--supabase local|hosted`, `--locales`,
-`--url`, `--publishable-key`, `--secret-key`, `--editor-email` (password from
-`SMOODLY_EDITOR_PASSWORD`), `--skip-link`, `--yes`. `--help` lists them.
-`--cloud` takes a Smoodly Cloud space's three values as a hosted project and
-skips `supabase init`, link, `db push` and the first editor: the shared
-project is migrated by Smoodly Cloud and the space's owner is its admin.
-A hidden `--smoodly-dep <spec>` overrides the `smoodly` dependency written into
-`package.json`; CI points it at the packed tarball.
+Then it installs, writes the env file, runs `npx smoodly push` (the schema
+to the space), `npm run seed` (the starter content through the API) and
+commits. A failed push or seed keeps the folder and prints the command that
+finishes it; a failed install removes the folder.
+
+Every prompt has a flag, so CI can run it: `--framework`, `--locales`,
+`--starter`, `--space`, `--secret-key`, `--publishable-key`, `--yes`.
+`--help` lists them. Hidden flags for the repo's loop and CI:
+`--api-url <url>` writes `SMOODLY_API_URL` (another service than
+Smoodly's), and `--smoodly-dep <spec>` overrides the `smoodly`
+dependency written into `package.json`; CI points it at the packed tarball.