尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 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.