@podosoft/podokit 1.4.0 → 1.4.2

package/dist/templates/todo/AGENTS.md

@@ -27,7 +27,7 @@ Provider selection does not migrate or delete existing data.
 ```bash
 {{packageManager}} install
 cp .env.example .env
-{{apiRun}} migration:run
+{{apiRun}} migrate:all
 {{rootRun}} dev        # api on http://localhost:5002, web on http://localhost:5001
 ```
 
@@ -50,10 +50,17 @@ Merge added module settings from `.env.example` into an existing `.env`.
   `apps/web/src/lib/server/body-limits.ts` (`APP_BODY_LIMITS`, 413
   `PAYLOAD_TOO_LARGE`). `BODY_SIZE_LIMIT` is the ceiling for every web route, so
   uploads larger than it must use a direct API path (`apiPaths`) instead.
+- When the root layout or a server hook fails, such as with 503 while the API is
+  down, SvelteKit serves the app-owned `apps/web/src/error.html`. It is plain HTML
+  with inline styles: no components, app CSS, scripts, or assets, and only the
+  `%sveltekit.status%` and `%sveltekit.error.message%` placeholders.
 - Build: `{{rootRun}} build`  ·  Type-check/lint: `{{rootRun}} lint`  ·  Unit tests: `{{rootRun}} test`
 - Per workspace: `{{apiRun}} build` / `{{webRun}} build`.
-- Application migrations (PostgreSQL or SQLite): `{{apiRun}} migration:run`.
-- When `auth` is installed, run `{{apiRun}} migrate:all` for Better Auth and application tables.
+- Set up the database and apply later migrations, including after adding a module, with
+  `{{apiRun}} migrate:all` (PostgreSQL or SQLite). With `auth` installed it applies the
+  Better Auth schema before the application migrations. `{{apiRun}} migration:run` runs
+  only the application migrations and never creates Better Auth tables;
+  `{{apiRun}} migration:revert` reverts the latest application migration.
 - e2e (Playwright, ships in `tests/`): `{{rootRun}} test:e2e`.
 - Playwright officially runs on Node, so `bunx playwright` respects its Node
   shebang. Node LTS is a test-tool dependency only; API, web, worker, migrations,

package/dist/templates/todo/README.md

@@ -78,7 +78,7 @@ defaults in the example and credentials only in `.env.docker`.
 In a second terminal, apply the included Todo migration and use the lifecycle helpers:
 
 ```bash
-{{packageExecutor}} @podosoft/podokit dev exec api {{apiRun}} migration:run
+{{packageExecutor}} @podosoft/podokit dev exec api {{apiRun}} migrate:all
 {{packageExecutor}} @podosoft/podokit dev url
 {{packageExecutor}} @podosoft/podokit dev up -d # detached stack without source watching
 {{packageExecutor}} @podosoft/podokit dev ps
@@ -113,7 +113,7 @@ web and API processes on the host. Prepare the project first:
 ```bash
 {{packageManager}} install
 cp .env.example .env
-{{apiRun}} migration:run
+{{apiRun}} migrate:all
 ```
 
 For PostgreSQL, start `docker compose -f infra/docker/docker-compose.yml up -d`
@@ -131,7 +131,7 @@ Run each service in a separate terminal from the project root:
 ```
 
 - API: http://localhost:5002 — health at `/health`, docs at `/api-docs`
-- Web: http://localhost:5001
+- Web: http://localhost:5001 — its own health at `/healthz`, which never calls the API
 
 For multi-project routing, container profiles, and OAuth over a stable HTTPS
 tunnel, see the PodoKit [development guide](https://github.com/podosoft-dev/podokit/blob/main/docs/development.md).
@@ -143,13 +143,15 @@ runs PostgreSQL migrations; SQLite uses the local migration runner. A sample
 Todo repository and initial migration are included.
 
 ```bash
-{{apiRun}} migration:run      # apply migrations
-{{apiRun}} migration:revert   # roll back the last one
+{{apiRun}} migrate:all        # set up the database and apply new migrations
+{{apiRun}} migration:revert   # roll back the last application migration
 ```
 
-When `auth` is installed, use `{{apiRun}} migrate:all` to create or update both
-Better Auth and application tables. Set the module's required environment
-values before migrating.
+`migrate:all` is the one command for setup, after adding a module, and in
+production. When `auth` is installed, it applies the Better Auth schema before
+the application migrations, so set the module's required environment values
+first. `{{apiRun}} migration:run` runs only the application migrations and
+never creates Better Auth tables.
 
 ## Deploy
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@podosoft/podokit",
-  "version": "1.4.0",
+  "version": "1.4.2",
   "description": "An opinionated Bun and Elysia full-stack TypeScript starter toolkit and CLI with SvelteKit, TailwindCSS, shadcn-svelte, Docker, and k3s.",
   "license": "Apache-2.0",
   "repository": {

package/dist/templates/modules/auth/files/apps/api/scripts/run-migrations.mjs

@@ -1,14 +0,0 @@
-import { existsSync } from "node:fs";
-import { fileURLToPath } from "node:url";
-
-const compiledEntry = new URL("../dist/migrate.js", import.meta.url);
-const sourceEntry = new URL("../src/migrate.ts", import.meta.url);
-const useCompiled = process.env.NODE_ENV === "production" && existsSync(compiledEntry);
-const entry = useCompiled ? compiledEntry : sourceEntry;
-const subprocess = Bun.spawn([process.execPath, fileURLToPath(entry)], {
-  stdin: "inherit",
-  stdout: "inherit",
-  stderr: "inherit",
-});
-
-process.exitCode = await subprocess.exited;