Skip to content

Conversation

ns-rboyd
Copy link
Contributor

Closes #5240

📑 Description

Adds the ability to use a custom schema name instead of public when using postgres db.

- Add POSTGRES_SCHEMA environment variable to configure non-public schemas
- Fix hardcoded 'public' schema reference in migration to use current_schema()
- Update db_utils.py to set search_path when POSTGRES_SCHEMA is configured
- Document schema configuration in deployment guide with setup instructions

Enables Keep to work in environments requiring specific PostgreSQL schemas
for multi-tenant deployments or shared database scenarios.
Copy link

vercel bot commented Aug 12, 2025

@ns-rboyd is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. Feature A new feature labels Aug 12, 2025
@ns-rboyd ns-rboyd changed the title Support for PostgreSQL custom schema configuration feat: Support for PostgreSQL custom schema configuration Aug 12, 2025
Copy link

vercel bot commented Aug 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
keep Ready Ready Preview Comment Aug 20, 2025 1:42pm

@sakharovmaksim
Copy link

+1 really looking forward to this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature A new feature size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[➕ Feature]: Add support for PostgreSQL custom schema configuration

3 participants