Fix Docker sidebar and chat history persistence#791
Merged
Conversation
- Use getCurrentUserId() instead of Supabase user for sidebar visibility and hasUser context, so sidebar and trigger button appear in anonymous mode (ENABLE_AUTH=false) - Override DATABASE_RESTRICTED_URL in docker-compose to prevent cloud DB connection strings from .env.local taking precedence over the local Docker PostgreSQL Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cb3d6eacd4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
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
ENABLE_AUTH=false) by usinggetCurrentUserId()instead of Supabase user forhasUsercontext andAppSidebarrenderingDATABASE_RESTRICTED_URLin docker-compose to prevent cloud DB connection strings from.env.localtaking precedence over the local Docker PostgreSQLBackground
In Docker deployments with
ENABLE_AUTH=false, two issues prevented chat history from working:Sidebar not visible:
AppSidebarandSidebarTriggerwere gated on!!user(Supabase auth), which is alwaysnullwhen Supabase is not configured. Changed to!!userIdfromgetCurrentUserId(), which returnsdocker-anonymousin anonymous mode.DB connection failure:
DATABASE_RESTRICTED_URLfrom.env.local(pointing to a cloud DB like Neon) was taking precedence over the Docker-localDATABASE_URLdue to the app preferringDATABASE_RESTRICTED_URLvia nullish coalescing. Now explicitly set in docker-compose to use the local PostgreSQL.Test plan
docker compose up -d --buildstarts successfully🤖 Generated with Claude Code