82680d9430
deploy/README.md described a rewrites() block that no longer exists, and told the reader to verify the image bucket's anonymous-download policy was set - which is precisely the exposure that was closed. Following it would have re-opened every stored image to the public internet. Replaced with what is actually true: /minio-images is a session-gated route handler with per-user key-prefix ownership, the bucket must have no anonymous policy, and MinIO must stay bound to loopback. Also noted that the suggested `mc anonymous get` check does not work on this host - the alias has no credentials and returns Access Denied either way - and gave an external curl that actually tells you something. The same stale rationale sat in deploy.sh's build comment. Building without the env file is still right, just for a different reason: nothing needs baking in. Added the MCP and OAuth journal greps, an unauthenticated discovery check, and a note that a 307 there means /.well-known fell out of PUBLIC_ROUTES. Documented in .env.example that NEXTAUTH_URL must be the exact public origin with no trailing slash, since it is now the OAuth issuer and MCP resource identifier, plus the MCP_CHATGPT_TOOLS opt-out. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1Ee4Mc1X1SX8HgYa52zu7
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
AI Gateway (Switchboard)
All AI features — menu scanning, label identification, drink search, the bartender
and the recommendation engine — go through Switchboard,
an OpenAI-compatible gateway that routes each request to the best available model.
The app never pins a model id; it always sends switchboard/auto and lets the gateway
choose, then logs which model answered and what it cost.
Setup:
- Set
SWITCHBOARD_BASE_URLin your env file (defaults tohttp://192.168.2.11:8787/v1). - Mint an API key in the Switchboard UI under Settings → API keys.
- Add that key in the app under Settings → AI Gateway.
Per-feature routing (cost/quality levers, token budgets, timeouts) lives in
src/lib/ai/routing.ts. Note that a Switchboard key carries its own routing defaults,
so the app sets category and prefer_free explicitly on every request rather than
inheriting whatever the key was minted for.
Migrating from the old Claude/OpenAI integration
Earlier versions stored a per-user Anthropic or OpenAI key. Those rows are ignored at runtime and the Settings page offers to remove them, so no migration is required. To clear them in bulk instead:
DELETE FROM "UserApiKey" WHERE provider IN ('claude','openai');
DELETE FROM "SearchCache" WHERE provider IN ('claude','openai');
UPDATE "UserPreference" SET "defaultProvider" = NULL;
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.