clarify application runtime modes

This commit is contained in:
2026-08-13 17:24:29 -05:00
parent 2760ae1ab8
commit 37042c0562
+4 -5
View File
@@ -5,7 +5,7 @@ portable import/export format, but normal application saves do not modify it.
Derived nutrition and cost are still calculated rather than stored.
Create the initial database from the current portable dataset with Node 22 or
newer, then run the site and application:
newer, then run either application mode:
```sh
npm run db:reset
@@ -13,10 +13,9 @@ npm run dev:readonly
npm run dev:app
```
Read-only mode serves the application with SQLite opened read-only. Development,
checks, and builds run it automatically. Successful application edits refresh
the same file, allowing the local Astro site to hot-reload database changes while
remaining read-only.
Read-only mode serves the same application with SQLite opened read-only, removes
editing controls, and rejects modifying HTTP requests. Browser-side scaling,
unit conversion, nutrition, and costing calculations remain available.
The database is written to `var/recipe-book.sqlite` and is intentionally ignored
by Git. `migrations/001_initial.sql` defines the complete relational schema.