Repository navigation
Fix BACKEND_URL docs and frontend env setup - #4
Merged
Merged
Conversation
Replace stale NEXT_PUBLIC_BACKEND_URL references with the current server-side proxy model. Update README, error copy, and setup scripts to create frontend/.env.local from the example so local dev works out of the box. Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Align turn_workflow and database unit tests with topic-only RAG queries and opt-in neighbor enrichment (neighbor_window=1) - Fail production frontend builds when BACKEND_URL is unset - Correct backend README retrieval notes to match current behavior Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
Align architecture and prompt-construction docs with the runtime default in settings.py and .env.example. Note that larger models remain available via LLM_MODEL_ID when quota allows. Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
Mark agt_010, agt_015, and agt_016 as unavailable until their source material is ingested. Filter them from default councils and saved selections, block drafting in the controller, and show them as disabled 'Corpus pending' options in the speaker roster. Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
Detect localhost BACKEND_URL on Vercel, map Vercel auth HTML to a clear proxy error, show council load failures in the UI, and document Preview environment requirements. Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
…atch Co-authored-by: Dimitrios Ntempos <dimitriosntempos@gmail.com>
This branch was successfully deployed
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
2 participants
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
Aligns documentation and setup with the current Next.js proxy architecture, fixes CI-blocking backend test drift, and adds production build validation for
BACKEND_URL.Changes
Documentation & setup
NEXT_PUBLIC_BACKEND_URLguidanceBACKEND_URLandBACKEND_API_KEYfrontend/.env.localfrom exampleProduction hardening
BACKEND_URLis missingCI fix
fetch_context_messages, and opt-inneighbor_window=1enrichmentVerification
python -m unittest discover -s backend/tests— 66 tests passBACKEND_URL=http://localhost:8000 npm run build— succeeds