Easy-to-manage touch screens
무료 오픈소스 터치스크린으로 USB 설정 가이드, 드래그‑드롭 편집기, 로컬 제어를 제공하며 Home Assistant용으로 제작되었습니다
Chiang Mai에서 AI로 173개 카페를 가격·거리·주차·음료로 필터링하고 리뷰 요약을 확인하세요
Find the right café in Chiang Mai: ask the AI finder in Thai or English, filter 173 real cafés by price, distance, parking and drink, and read AI review summaries.
라이프스타일TypeScript · PythonGitHub @sjsiwat온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Most existing café discovery platforms focus on location and ratings.
BrewMap AI focuses on taste.
Instead of helping users find the nearest café,
we help them find the right café.
Finding a good café is surprisingly difficult.
Current platforms such as Google Maps provide thousands of reviews and high ratings, but they rarely answer questions like:
Which café serves the best latte?
Which café specializes in pour-over coffee?
Which matcha café is worth visiting?
Which café is quiet enough to work from?
Which café has parking?
Which café serves chocolate-forward coffee instead of fruity coffee?
Users often spend 20–30 minutes reading reviews before deciding where to go.
Most review platforms also categorize cafés by location rather than by coffee experience.
As a result, people frequently visit cafés that don't match their preferences.
BrewMap AI helps users discover cafés through taste-first recommendations.
Instead of asking:
"Where should I go?"
We ask:
"What kind of coffee are you looking for today?"
The AI analyzes user preferences and recommends cafés based on:
Coffee style
Flavor profile
Brewing method
Atmosphere
Budget
Distance
Community reviews
Coffee lovers
Specialty coffee beginners
Tourists
Digital nomads
Remote workers
Matcha lovers
Café hoppers
BrewMap AI is an AI-powered coffee discovery platform designed to help people find cafés based on their personal taste—not just ratings.
Instead of scrolling through hundreds of Google Maps reviews or generic ranking websites, users can describe what they are looking for in natural language, and AI recommends the most suitable cafés.
The project combines interactive maps, AI recommendations, coffee knowledge, and community-driven reviews into a single experience.
Display cafés on an interactive map.
Each café marker includes:
Photos
Rating
Coffee specialties
Opening hours
Quick description
Directions
Browse cafés by category.
Examples:
Latte
Flat White
Espresso
Pour Over
Cold Brew
Matcha Latte
Ceremonial Matcha
Dessert Café
Roastery
Pet Friendly
Curated rankings such as:
Top 10 Latte
Top 10 Pour Over
Top 10 Matcha
Top Hidden Cafés
Top Coffee Roasters
Best Cafés for Working
Best Scenic Cafés
Users simply describe what they want.
Example:
I want a quiet café near Nimman with creamy latte, parking, and good Wi-Fi.
The AI recommends cafés and explains why each one matches.
Search by:
Coffee type
Flavor notes
Brewing method
Atmosphere
Budget
District
Distance
Users can bookmark cafés for future visits.
Instead of reading 2,000 reviews, AI summarizes them.
Example:
Pros
Excellent dirty coffee
Friendly staff
Quiet atmosphere
Cons
Limited parking
Long waiting time on weekends
Each café page includes:
Gallery
Coffee menu
Matcha menu
Signature drinks
Flavor profile
Recommended drinks
Facilities
Business hours
Location
Reviews
The system learns user preferences over time.
Example:
The user usually likes:
Chocolate notes
Low acidity
Milk coffee
Quiet cafés
Future recommendations become increasingly personalized.
Cafés can pay to promote their business within search results.
Business dashboard including:
Analytics
Customer insights
AI-generated review summaries
Marketing tools
Recommend coffee beans, brewing equipment, and accessories.
Promote coffee festivals, workshops, and cupping events.
Most existing café discovery platforms focus on location and ratings.
BrewMap AI focuses on taste.
Instead of helping users find the nearest café,
we help them find the right café.
Become the smartest AI-powered coffee discovery platform for specialty coffee lovers.
Start with Chiang Mai.
Expand to cities across Thailand.
The repo has two apps: web/ (Next.js) and server/ (NestJS API on MongoDB Atlas).
# 1. install root + both apps
npm install
npm run install:all
# 2. env files
cp server/.env.example server/.env # fill in MONGODB_URI
cp web/.env.example web/.env.local # API_URL=http://localhost:4000/api
# 3. load café data into MongoDB (safe to re-run)
npm run seed
# 4. start web + api together
npm run dev
/en or /th)npm run build in web/ prerenders every café page from the API, so keep the server running while building (if it is down, the build still succeeds and pages render on first request).
For the AI Finder and review summaries, also set GEMINI_API_KEY and GEMINI_MODEL in server/.env (npm --prefix server run ai:models lists the models your key can use). Without them the rest of the site works and the finder says it is unavailable.
flowchart LR
B[Browser] -->|pages + /api/*| V[Next.js on Vercel<br/>web/]
V -->|"/api/* rewrite (same-origin cookie)<br/>+ x-client-ip, x-proxy-secret"| R[NestJS API on Render<br/>server/]
V -.->|build + ISR: café pages| R
R --> M[(MongoDB Atlas<br/>cafes · users · favorites · reviews · google_reviews)]
R -->|AI Finder: filters + reasons| G[Gemini API]
S[ai:summarize script] -->|review text + stars only| G
S --> M
/api/* is rewritten to the API, so the login cookie (httpOnly, Secure, SameSite=Lax) is first-party.PROXY_SECRET, so rate limits apply per visitor, not per Vercel server./en/… or /th/… (web/app/[lang]). A path without one (/cafes) redirects using the visitor's last choice (NEXT_LOCALE cookie), else their browser language, else English. UI text is in web/lib/i18n/en.ts and th.ts. Café text comes from the API with ?lang=th (specialty, flavor, atmosphere and AI summary, translated once by ai:translate); tag and area names are translated in th.ts, and café names and addresses stay as listed.| URL | |
|---|---|
| Web | https://brewmap-cafe.vercel.app |
| API health | https://brewmap-api.onrender.com/api/health |
| API docs | off in production; run locally at http://localhost:4000/api/docs, or set SWAGGER=true on the API |
The API goes first, because the web build reads café data from it.
1. MongoDB Atlas: Network Access → add 0.0.0.0/0. Render's free tier has no fixed outbound IPs, so the database user's password is the protection. Use a long random password.
2. API on Render: New → Blueprint → this repo (render.yaml). When Render asks for the secret values:
| Key | Value |
|---|---|
MONGODB_URI | Atlas connection string (database brewmap) |
GEMINI_API_KEY | from Google AI Studio |
PROXY_SECRET | openssl rand -hex 32. The same value goes on Vercel. |
WEB_ORIGIN | the Vercel URL, e.g. https://brewmap.vercel.app. Fill it in after step 3. |
JWT_SECRET is generated by Render. Check https://<api>.onrender.com/api/health → {"status":"ok","database":"connected"}.
3. Web on Vercel: Add New → Project → this repo, Root Directory web, then set these environment variables:
| Key | Value |
|---|---|
API_URL | https://<api>.onrender.com/api. It must end in /api; without it every API call and café page returns 404. |
PROXY_SECRET | the same value as on Render |
4. Data: the café data, AI summaries and Google reviews already live in Atlas. If you point to a new cluster, run these with that MONGODB_URI:
npm run seed # cafés
npm --prefix server run import:google-reviews # Google reviews: stars, text, date only
npm --prefix server run import:opening-hours # weekly opening hours (open now)
npm --prefix server run ai:summarize # AI pros/cons (uses Gemini)
npm --prefix server run ai:translate # Thai text for each café (uses Gemini; after ai:summarize)
Render's free tier sleeps after 15 minutes idle, so the first request after that takes about 30–60 s.