Docs/honesty pass#7
Merged
Merged
Conversation
- README: corrected the dashboard-index field name from `(user_id, created_at)` to `(chatId, createdAt)` to match prisma/schema.prisma. There is no User model — the composite index is on Message(chatId, createdAt). - README: added the schema-recovery story (commit b85d4f5 dropped the Chat/Message/GeneratedApp block; recovered from b85d4f5^ with `npx prisma validate` before re-committing — recovery commit is 34b9565). - README: replaced the unmarked "Live Demo" block with a status note + link to the deployment runbook. - README: surfaced Sandpack rendering, Mistral support, and the Neon serverless adapter (all already in package.json + route code). - prisma/optimization.md: expanded the 1-line stub into a real before/after with the actual `findMany` query, the EXPLAIN ANALYZE command to reproduce, and an honesty caveat that the 25% number is a single local measurement, not a load test. Every claim in the rewritten README traces to a code file in this repo.
- deployment.md: replaced the 1-line stub with a runbook covering env-var setup (DATABASE_URL, GEMINI_API_KEY, MISTRAL_API_KEY, optional S3 vars), the automatic `prisma migrate deploy` step in the build script, schema-change workflow, code-only and code+schema rollback paths, and a smoke-test checklist. Includes the real schema-recovery sequence (`git show b85d4f5^:prisma/schema.prisma > prisma/schema.prisma && npx prisma validate`) as the hard-recovery example. - .env.example: replaced the wrong `OPENAI_API_KEY` (the project uses Gemini and Mistral, not OpenAI) with `GEMINI_API_KEY`, `MISTRAL_API_KEY`, and the optional S3_UPLOAD_* vars used by `app/api/s3-upload/route.ts`. Updated the DATABASE_URL example to include `?sslmode=require` for Neon.
❌ Deploy Preview for devscodex failed. Why did it fail? →
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.