Easy-to-manage touch screens
무료 오픈소스 터치스크린으로 USB 설정 가이드, 드래그‑드롭 편집기, 로컬 제어를 제공하며 Home Assistant용으로 제작되었습니다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.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.