feat: pass pgrst config to studio container

[charislam]

What kind of change does this PR introduce?

Enhancement

What is the current behavior?

Studio does not have access to PGRST configuration.

What is the new behavior?

Studio has access to PGRST configuration variables, to display the API integrations read-only settings in local dev.

Additional context

Needed for supabase/supabase#43268

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Cache: Disabled due to Reviews > Disable Cache setting

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between c42f41f and 30592a5.

📒 Files selected for processing (1)

• internal/start/start.go

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Added PostgREST environment variables to container startup to allow configuring DB schemas, extra search path, and maximum rows returned—enabling finer database behavior control for deployed containers.

Walkthrough

The pull request adds three PostgREST environment variables—PGRST_DB_SCHEMAS, PGRST_DB_EXTRA_SEARCH_PATH, and PGRST_DB_MAX_ROWS—to two container environment blocks in internal/start/start.go (the Studio container and an earlier Studio startup code path). No control-flow, error-handling, or other functional changes were made.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}