Add Supabase Cloud DBM setup page and link to Postgres setup#35276
Add Supabase Cloud DBM setup page and link to Postgres setup#35276dalextorres wants to merge 9 commits intomasterfrom
Conversation
The Supabase setup guide existed but was not linked from the Postgres setup landing page. Add the card and logo. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Split Supabase DBM docs into two sub-pages mirroring the RDS pattern: - Supabase Cloud (_index.md): integration tile setup, no Agent required - Supabase Self-Hosted (agent.md): existing Agent-based setup Also adds Supabase Cloud and Supabase Self-Hosted menu entries. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
github-actions
bot
added
Architecture
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 21c79c64bf
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| parent: dbm_postgres_supabase | ||
| identifier: dbm_supabase_cloud |
There was a problem hiding this comment.
These new entries are attached under dbm_postgres_supabase, which creates a fourth navigation level, but the left-nav renderer hides level-4 submenus with d-none unless the parent identifier is explicitly allowlisted (layouts/partials/nav/left-nav.html, around lines 69-72, currently only includes dbm_setup_postgres_rds for this DBM section). Because dbm_postgres_supabase is not in that allowlist, the new “Supabase Cloud”/“Supabase Self-Hosted” items will not appear in the sidebar even when Supabase is expanded, so users can’t discover them through primary docs navigation.
Useful? React with 👍 / 👎.
Without this, the Supabase Cloud and Supabase Self-Hosted sub-menu items are hidden by d-none in the sidebar. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Preview links (active after the
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Keep both dbm_postgres_supabase (ours) and dev_tool_int_mcp_server (master). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2 participants
What does this PR do? What is the motivation?
/database_monitoring/setup_postgres/)static/images/integrations_logos/_index.md): Setup through the Supabase integration tile — no Agent requiredagent.md): Existing Agent-based setup (moved fromsupabase.md)Merge instructions
Merge readiness:
Additional notes
The Supabase Cloud page documents the integration tile flow (Project ID, API Key, Personal Access Token, "Enable Database Monitoring for query performance optimizations" checkbox) and the specific telemetry collected (query performance metrics, query samples, database instance metadata).
🤖 Generated with Claude Code