Easy-to-manage touch screens
Free, open-source touch screens. Guided USB setup, a drag-and-drop editor and local control. Made for Home Assistant.
Personal homebrewing journal: recipes, brew sessions, problems and lessons learned.
Translation pending
LifestyleTypeScript · CSSGitHub @pao1230OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Personal homebrewing journal: recipes, brew sessions, problems and lessons learned — so each
batch learns from the last one. See PLAN.md for the full product plan.Read the full README ↗Personal homebrewing journal: recipes, brew sessions, problems and lessons learned — so each batch learns from the last one. See PLAN.md for the full product plan.
Phases 1–3 are implemented:
Next.js 16 (App Router, Server Actions) · React 19 · TypeScript · Tailwind CSS 4 · PostgreSQL · Prisma 7 · Vitest
cp .env.example .env
docker compose up -d # Postgres on localhost:5432 (or point DATABASE_URL at your own)
npm install # also runs `prisma generate`
npm run db:migrate # create tables
npm run db:seed # optional: Sweet Stout recipe + brew #001 + starter ingredients
npm run dev # http://localhost:3000
| Script | |
|---|---|
npm run dev / build / start | Next.js |
npm run typecheck | Route type generation + tsc |
npm run lint | ESLint |
npm test | Unit tests (brewing math, calculators, inventory, CSV, scaling, search) |
npm run db:migrate | Create/apply a migration in development |
npm run db:deploy | Apply migrations in production |
npm run db:seed | Seed sample data (skipped if the DB already has data) |
Starter ingredients (166 malts, hops, yeasts, water salts and additives from the Thai shops WAS Homebrew and Craft Components) live in src/lib/catalog-data.ts. The seed adds them, and on an existing database the Ingredients page offers an Add them button that adds only the ones you don't have yet.
There is no login (single-user): anyone who has the app's address can see and change everything. Keep the address private, or put it behind your host's own access protection (e.g. Vercel Deployment Protection).
Vercel + Supabase:
| Vercel env var | Value |
|---|---|
DATABASE_URL | Supabase transaction pooler URL (port 6543) — used by the app |
DIRECT_URL | Supabase session pooler URL (port 5432) — used by migrations |
If you connect Supabase through Vercel's Supabase integration instead, nothing needs copying: the
app also reads the integration's POSTGRES_PRISMA_URL / POSTGRES_URL (app) and
POSTGRES_URL_NON_POOLING (migrations), and treats their sslmode=require as "encrypted,
certificate not verified" like psql does.
Supabase's direct host (db.<ref>.supabase.co) is IPv6-only and unreachable from Vercel. When the
migration URL points there, migrations use the session pooler instead (the pooled URL's host and
user on port 5432), so a P1001 "Can't reach database server at db.….supabase.co" no longer
happens.
Set the Build Command to prisma migrate deploy && next build so each deploy applies new
migrations first (a failed migration fails the deploy and the previous version stays live).
Set the function region to Singapore (sin1) to sit next to the database, and turn off
Supabase's Data API — the app doesn't use it.
prisma/schema.prisma data model (see PLAN.md §25)
src/lib/brewing.ts step definitions, formatting, ABV/volume math, validation
src/app/ingredients ingredient master
src/app/equipment equipment profiles
src/app/recipes recipe list/detail/editor + versioning actions
src/app/brews sessions, steps, problems, lessons (actions.ts has all mutations)
src/app/compare side-by-side brew comparison
src/app/lessons knowledge-base search (problems, lessons, notes)
src/components/line-chart dependency-free SVG line chart
src/lib/search.ts query parsing, filters, highlighting
src/lib/calc.ts IBU/SRM/OG/FG, water profile, efficiency, priming sugar
src/lib/inventory.ts stock ledger math and costing
src/lib/i18n translations: English text is the key, th.ts has the Thai;
getI18n() on the server, useI18n() in client components
src/app/inventory inventory page, stock card, inventory actions
Wrap UI text in t("…") (server: const { t } = await getI18n(), client: useI18n()), with
{placeholders} for values, and add the Thai to src/lib/i18n/th.ts. npm test fails if a
string in the source has no Thai translation or a translation drops a placeholder.