Skip to content

Feat/label qr and tailscale - #563

Open
Brandon2255p wants to merge 6 commits into
keptinventory:mainfrom
Brandon2255p:feat/label-qr-and-tailscale
Open

Brandon2255p wants to merge 6 commits into
keptinventory:mainfrom
Brandon2255p:feat/label-qr-and-tailscale

Conversation

@Brandon2255p

Copy link
Copy Markdown

What and why

Checks

  • bash scripts/ci-local.sh passes (or --fast, and say which steps you couldn't run)
  • Tests first, on their own database; the leak test and route catalogue updated for a new table or route
  • Migrations are additive (a drop or rename takes two releases)
  • New strings in every catalogue, Arabic in the house style; logical CSS; works at 375 px and 1280
  • Conventional commit messages; no AI attribution in commits or this description (D173)
  • The CLA signed (once, on your first pull request; see CONTRIBUTING.md)

Helpers copied between modules now live in one place, unchanged in
behaviour:

- purchases uses money/input.ts's amountIn, currencyIn, requireEnabled,
  todayIn and moneyOff instead of its own copies; schedules re-exports
  todayIn from there, and money/input.ts re-exports things/validate.ts's
  moneyOff.
- safeTimeZone, copied into four report views and the incident report,
  is reports/locale.ts's.
- requireVersion, copied into fuel, schedules, service records and
  things, is audit/undo.ts's requireRowVersion(client, entityType, ...).
- optionalIfMatch, identical in meters, things and moves, is
  http/conventions.ts's. places/routes.ts keeps its own: it also treats
  an empty If-Match as absent.
A label's QR holds `<public-url>/l/<code>`, so a long domain makes a
dense QR: 29 modules a side for a tailnet name, 33 for a longer domain.
The print screen now asks what the QR holds: the link (the default, any
phone camera opens it) or the code alone, 21 modules, the smallest QR
there is. Only Kept's scanner reads that one; shared/scan.ts already
takes a bare code as a Kept label, so labels of both kinds keep working.

The choice is remembered on this browser, like the stock, and shown only
for stocks that print a QR. The sheet, its preview and the phone PNGs
all follow it. Five strings, in every catalogue.
compose.yaml with no published port: Kept is reachable only through a
tailscale service that serves it over HTTPS on the tailnet, with a
Tailscale certificate and Funnel off. Serve proxies to the kept-app alias
and the tailscale container has no hostname, so the proxy cannot resolve
to itself and loop. The kept service also gets the owner URL and the
kept-owner volume (read-only) for the nightly backup.

A separate file, so compose.yaml and compose.full.yaml stay as they are.
fork-image.yml builds the Dockerfile's runtime target for amd64 and arm64
and pushes ghcr.io/<owner>/kept, so an install runs the fork with
KEPT_IMAGE in .env. Tags: the branch, sha-<commit>, and latest from main.
The version is upstream's last release with the commit as build metadata
(1.14.7+fork.abc1234), and the image's source labels name this fork.
Skipped in keptinventory/kept, which publishes through release.yml.
@Brandon2255p
Brandon2255p requested a review from a team as a code owner November 15, 2026 19:45
@github-actions

Copy link
Copy Markdown


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

release_history_version_chk takes a prerelease and refuses a +, so an
image versioned 1.14.7+fork.<commit> failed kept migrate as it recorded
the release, and kept, waiting on migrate, never started. Fork images are
now <next patch>-fork.<commit> (1.14.8-fork.abc1234): after the release
they are built on, before upstream's next.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant