5
Enhancing Twenty for Supabase Compatibility: Custom Database Configurations, Schema Adjustments, and S3 Storage Integration
Source: twentyhq/twenty#5449 · opened by @rickylabs
Scope & Context We aim to integrate Twenty into an existing ecosystem utilizing a Supabase instance that already supports various applications like Medusa, Strapi, and Directus. The integration requires customization of Twenty's database configurations to ensure compatibility with Supabase's infrastructure, including schemas, user permissions, extensions location, and storage options. Current Behavior and Process Adjustments in the database setup and Docker configuration were necessary to align Twenty with our self-hosted Supabase instance. The process highlighted the potential for compatibility with some codebase adjustments: 1. Database Migration Adjustments: Created a restricted Twenty user to avoid dropping existing schemas. Manually set up required schemas and utilized pre-installed extensions in Supabase, indicating a need for customizable schema and extension locations. 2. Docker Compose Modifications: Updated the docker-compose.yml to connect Twent…
No pledges yet. Be the first to back this.
Comments
Similar requests
Would Telvine-style distribution/evals help Twenty’s existing agent plugin and Skills?
1 vote · 0 comments
Add easier integration to n8n, zapier, make and easier custom workflows
5 votes · 0 comments
Would an Inbox Zero × Twenty integration be useful?
2 votes · 0 comments
I created a Twenty MCP Server - Looking for Feedback!
3 votes · 0 comments
Where should a CRM reminder live? Proposal: two-way calendar sync so follow-ups land in the user's own calendar
6 votes · 0 comments
No comments yet.