Tag non-production tabs, and drop the FOODSTER_ prefix

With dev and prod open side by side in the same browser, the tabs were indistinguishable. ENV is written into the title of every page unless it says prod, so "dev · Foodster" picks itself out. The value is used verbatim, so ENV=staging labels itself too, and prod and production both count as unmarked so a stray capital cannot tag the real instance. Environment variables lose their prefix: PASSWORD, DB, ENV, ADDR, HOST, REPO, TAG. The container namespaces them already, and this matches how the other services here are configured. PUID/PGID are the exception rather than UID/GID. UID is read-only in bash, so a value set in .env would be silently replaced by the invoking shell's own and compose's user: would ignore what was asked for. Breaking for a running instance: the deployed .env has to be rewritten in the same deploy, or the app will refuse to start on an unset PASSWORD.
Patch the day list in place instead of navigating
2026-09-05 23:55:25 +03:00 · 2026-09-05 23:45:53 +03:00 · 2026-09-05 23:40:22 +03:00 · 2026-09-05 23:35:45 +03:00
2 changed files with 0 additions and 97 deletions
@@ -1,94 +0,0 @@
 # Contributing
 A household project, so this is less a set of rules than a note to whoever
 picks it up next — including me in six months.
 ## Getting set up
 ```sh
 cp .env.example .env      # then edit it
 make run                  # http://localhost:8080, tab titled "dev · Foodster"
 make                      # every target, with a one-line description
 ```
 `make check` is the gate: `go vet`, gofmt, unit tests, and `scripts/smoke.sh`,
 which drives a real server over HTTP. Run it before every commit.
 ## Branches
 `dev` is where work happens. `main` holds released versions only — it is
 protected on the remote and takes no direct pushes, so a release arrives as a
 pull request from `dev`, squash-merged.
 After a squash merge, reset `dev` onto it or the next pull request will offer
 the same commits again:
 ```sh
 git switch main && git pull --ff-only
 git switch dev && git reset --hard main
 git push --force-with-lease origin dev
 ```
 `make image` refuses to run outside `main`. That check has to be local: the
 tag and the image are made before anything reaches the remote, so branch
 protection cannot catch a release built from the wrong branch.
 ## Commit messages
 Conventional Commits — a type, an optional scope, then a short subject in the
 imperative.
 ```
 feat(kirjaa): expand the selected day in place
 fix: redirect the catalog to /ruuat, not /ruoat
 chore(deps): bump the vendored Datastar client
 ```
 | Type | For |
 |---|---|
 | `feat` | new behaviour someone will notice |
 | `fix` | a bug, ideally naming what broke |
 | `refactor` | same behaviour, different shape |
 | `test` | tests only |
 | `docs` | documentation only |
 | `build` | Makefile, Containerfile, compose, CI |
 | `chore` | anything else: dependencies, seeds, tidying |
 **The body matters more than the type.** Explain *why*, and what the
 alternative was — the diff already says what changed. If a fix was subtle,
 say what made it subtle; if a test caught something, say what. Commits here
 are the only design record this project has.
 ### Release pull requests
 Because `main` is squash-merged, a pull request title becomes a commit message
 on `main`. A release spans a fix, a feature and some chores at once, so none
 of the types above fits it honestly. Use `release:` instead:
 ```
 release: repair the catalog 404 and stop the page jumping
 ```
 `main`'s log is then one line per deployment, which is what that branch is
 for, and the pull request body serves as the release notes. No version in the
 title — the CalVer tag is not created until `make image` runs after the merge.
 The types above are for `dev`, where a commit really does do one thing.
 ## Things that are easy to get wrong
 - **The interface is Finnish.** Code, comments, this file and the PRD are
  English. There is no i18n layer and no language switcher.
 - **No infrastructure detail is committed** — no hostnames, registry paths or
  ports. They live in `.env`, which is gitignored, because the PRD leaves the
  door open to publishing this repository.
 - **Migrations are immutable once shipped.** A released migration has run on a
  live database and will not run again. Add a new numbered file instead.
 - **Interactions patch, they do not navigate.** Anything that reloads the page
  loses the scroll position, which on a long list is maddening. Links stay
  links and forms stay forms so it works without JavaScript; Datastar layers
  over them with `data-on:click__prevent` and `data-on:submit__prevent`.
 - **A `ponytail:` comment marks a deliberate shortcut** and names its ceiling,
  so the next reader can tell a decision from an oversight.
 - **Assert what a response does, not just that it responded.** A redirect to a
  dead URL is still a 303; that one shipped.
@@ -58,9 +58,6 @@ One static Go binary. No Node.js, no bundler, no separate database server.
 | Auth | HTTP Basic, one shared household password |
 | Runtime image | `FROM scratch` |
 Working on it: [CONTRIBUTING.md](CONTRIBUTING.md) — branches, commit messages,
 and the conventions that are easy to miss.
 ## Branches
 `main` holds released versions only. Every release tag points at a commit on
Author	SHA1	Message	Date
Esa Kataja	c6a8532569	Tag non-production tabs, and drop the FOODSTER_ prefix With dev and prod open side by side in the same browser, the tabs were indistinguishable. ENV is written into the title of every page unless it says prod, so "dev · Foodster" picks itself out. The value is used verbatim, so ENV=staging labels itself too, and prod and production both count as unmarked so a stray capital cannot tag the real instance. Environment variables lose their prefix: PASSWORD, DB, ENV, ADDR, HOST, REPO, TAG. The container namespaces them already, and this matches how the other services here are configured. PUID/PGID are the exception rather than UID/GID. UID is read-only in bash, so a value set in .env would be silently replaced by the invoking shell's own and compose's user: would ignore what was asked for. Breaking for a running instance: the deployed .env has to be rewritten in the same deploy, or the app will refuse to start on an unset PASSWORD.	2026-09-05 23:55:25 +03:00
Esa Kataja	b8a46cdd30	Patch the day list in place instead of navigating Kirjaa now works like the catalog: opening a day, picking a dish, saving, deleting, cancelling and "Näytä lisää" all patch the list where it stands. Nothing loads a page, so the scroll position never moves. One builder serves all three paths. buildLog takes what the screen should show — the day, an open dish, whether the entry is being changed or a delete confirmed — and the page render, the patch and the post-write response all go through it. After a save it is called with only the date, so the day comes back closed rather than reopening the sides step it was just submitted from. Links stay links and forms stay forms, with data-on:click__prevent and data-on:submit__prevent layered over them, so it all still works with JavaScript off. Each response patches a single element, so plain text/html is enough here; the SSE writer is only needed by the catalog, where the list and both forms have to move together. The anchors added in the previous attempt are gone. They could never have worked: the browser positions an anchor without knowing where the page was scrolled, so it jumped regardless.	2026-09-05 23:45:53 +03:00
Esa Kataja	e5e020457a	Patch the catalog in place instead of navigating Deleting a dish partway down the list sent the browser back to the top. The first attempt at fixing it used anchors, which cannot work: the browser positions the element with no knowledge of where the page was scrolled, so it still jumps. Datastar was already loaded and doing nothing but search. Every catalog action now patches. The bin, the pencil and Peruuta stay real links; the forms stay real forms. Datastar intercepts them with data-on:click__prevent and data-on:submit__prevent, and the same handlers redirect when the Datastar-Request header is absent, so none of it requires JavaScript. Posting with {contentType: 'form'} sends the enclosing form as FormData, which means the handlers keep reading r.FormValue and no input had to be rewritten as a signal. The response is one SSE event carrying three elements: the list and both forms. They have to move together — opening an edit form also has to clear a delete that was mid-confirmation — and a text/html response can only replace one element. The writer is twenty lines rather than re-adding the SDK and the four modules it brings for a generator we would otherwise never call. Smoke checks assert the wire format: that these answer with an event stream carrying all three elements, that the deleted dish is absent from the patched list, and that a header-less post still redirects.	2026-09-05 23:40:22 +03:00
Esa Kataja	f8b908b39e	Fix catalog redirects pointing at the old /ruoat Adding, editing or deleting a dish redirected to /ruoat, which stopped existing when the tab was renamed to Ruuat. Every one of those actions ended on a 404. Shipped in v20260905-4. The rename was done with a scripted replace across views.templ, main.go and the smoke script; handlers.go was not in the list. The tests did not catch it because they asserted only that the response was a 303. A redirect to a dead URL is still a 303. They now assert the target.	2026-09-05 23:35:45 +03:00