fix(vercel): drop the legacy builds/routes config that conflicts with functions

Author: codebybilal18

.gitignore

@@ -7,7 +7,6 @@ __pycache__/
 *.egg-info/
 .venv/
 venv/
-.python-version
 
 .pytest_cache/
 .ruff_cache/

.python-version

@@ -0,0 +1 @@
+3.12

.vercelignore

@@ -0,0 +1,28 @@
+# Keep the serverless bundle under the 250 MB unzipped limit.
+#
+# Only api/ and app/ are needed at runtime. Everything below is development,
+# CI, or deployment tooling that would otherwise be uploaded and counted
+# against the limit.
+
+tests/
+k8s/
+.github/
+scripts/
+
+Dockerfile
+docker-compose.yml
+.dockerignore
+
+# Migrations run from a developer machine or CI, never from the function —
+# two concurrent instances racing the same migration is worse than a manual
+# step. The golden set and corpus are eval fixtures, not runtime data.
+alembic.ini
+evals/
+
+requirements-local.txt
+requirements-dev.txt
+
+README.md
+.venv/
+.ruff_cache/
+.pytest_cache/

README.md

@@ -313,14 +313,31 @@ cannot detect.
 
 ## Deploying to Vercel
 
-```bash
-vercel --prod
+Import the repo at vercel.com/new. Project settings:
+
+| Setting | Value |
+|---|---|
+| Application Preset | **FastAPI** |
+| Root Directory | `./` |
+| Install Command | `pip install -r requirements.txt` (the default) |
+| Build / Output | leave empty — [vercel.json](vercel.json) handles routing |
+
+Environment variables:
+
+```
+DATABASE_URL     postgresql://…-pooler….neon.tech/db?sslmode=require   # paste verbatim
+OPENAI_API_KEY   sk-…
+ACTIVE_CONFIG    serverless
+ENVIRONMENT      vercel
+CORS_ORIGINS     https://<your-frontend>.vercel.app
 ```
 
-Set `DATABASE_URL` (Neon, **pooled** connection string), `OPENAI_API_KEY`, `CORS_ORIGINS`, and
-`ACTIVE_CONFIG=serverless`. Run `alembic upgrade head` locally against the same database — the app
-does not migrate on boot, because two concurrent instances racing the same migration is worse than
-a manual step.
+`DATABASE_URL` is normalised on load, so the console's connection string works as-is — the driver
+is corrected and `sslmode`/`channel_binding` are translated into asyncpg connect arguments. Use the
+**pooled** host; the direct one exhausts connections under serverless.
+
+Run `alembic upgrade head` **locally** against that database first. The app does not migrate on
+boot, because two concurrent instances racing the same migration is worse than a manual step.
 
 ### What is different on serverless, stated plainly
 

vercel.json

@@ -1,21 +1,10 @@
 {
   "$schema": "https://openapi.vercel.sh/vercel.json",
-  "version": 2,
-  "builds": [
-    {
-      "src": "api/index.py",
-      "use": "@vercel/python",
-      "config": { "maxLambdaSize": "45mb", "runtime": "python3.12" }
-    }
-  ],
-  "routes": [{ "src": "/(.*)", "dest": "api/index.py" }],
   "functions": {
     "api/index.py": {
       "maxDuration": 60,
-      "memory": 1769
+      "includeFiles": "app/**"
     }
   },
-  "env": {
-    "ENVIRONMENT": "vercel"
-  }
+  "rewrites": [{ "source": "/(.*)", "destination": "/api/index" }]
 }