Aurora Travel Backend

Aurora Travel App — with backend

This version keeps your Anthropic API key on the server instead of exposing it in the browser. The frontend (in `public/`) now calls your own local backend (`/api/chat` and `/api/analyze`), which forwards requests to Claude using a key stored in an environment variable.

Setup

1. Install Node.js 18+ if you don't have it.
2. In this folder, install dependencies:

   npm install

3. Create your .env file from the example:

   cp .env.example .env

   Then open .env and paste in your real Anthropic API key.
4. Start the server:

   npm start

5. Open http://localhost:8787 in your browser. That's Aurora, fully working, with the key safely on the server.

What changed from the browser-only version

• public/index.html now calls /api/chat and /api/analyze (relative paths on your own server) instead of https://api.anthropic.com/v1/messages directly.
• server.js holds the actual Anthropic API key (from .env) and is the only place that ever talks to Anthropic. The browser never sees the key.
• The model name, max_tokens, and the web-search tool are now set server-side, so the client can't be tampered with to change them.

Notes

• .env is meant to stay on your machine — don't commit it or share it. Only .env.example (with no real key) should be shared or committed.
• If you ever deploy this somewhere public (Render, Railway, Fly.io, a VPS, etc.), set ANTHROPIC_API_KEY as an environment variable in that platform's dashboard rather than uploading your .env file.
• The service worker (sw.js) and manifest are unchanged from the earlier PWA packaging — they still let you "install" Aurora as an app once served over http(s).