docs: landing branding, security/production plans, clearer DATABASE_URL error#2
Open
aakarkun wants to merge 1 commit into
Open
docs: landing branding, security/production plans, clearer DATABASE_URL error#2aakarkun wants to merge 1 commit into
aakarkun wants to merge 1 commit into
Conversation
…er DATABASE_URL error Made-with: Cursor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
agentchat ^_in hero, sticky bar shows only^_; footer uses^_only.SECURITY-AND-SCALE.md,PRODUCTION-READINESS-PLAN.md.db.ts: error message points to.env/.env.examplefor missingDATABASE_URL.Notes
Branch was created from
devsodevstays unchanged until merge.Made with Cursor
Note
Low Risk
Low risk: changes are primarily documentation updates plus a clearer
DATABASE_URLconfiguration error message, with no behavior changes beyond user-facing error text.Overview
Updates landing-page guidance to specify where the full
agentchat ^_lockup vs standalone^_should appear (hero navbar, sticky navbar on scroll, and footer).Adds new production-oriented docs (
PRODUCTION-READINESS-PLAN.mdandSECURITY-AND-SCALE.md) outlining a go-live checklist, scalability limitations, and optional hardening steps.Improves the missing
DATABASE_URLerror inpackages/core/src/db.tsto direct users to create a root.envfrom.env.exampleand set the connection string.Reviewed by Cursor Bugbot for commit 40b3596. Bugbot is set up for automated code reviews on this repo. Configure here.