feat: init supabase

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• New Features
  • Introduced a .gitignore file to enhance project cleanliness by ignoring sensitive and temporary files.
  • Added a comprehensive config.toml file for customizing various aspects of the Supabase environment, including API settings, database configurations, authentication options, and more.
  • Expanded environment variable support with SUPABASE_URL and SUPABASE_ANON_KEY for improved integration with Supabase services.

These updates provide users with better project management and configuration capabilities, ensuring a more streamlined development experience.

[coderabbitai]

Walkthrough

This pull request introduces a .gitignore file to specify files and directories that should be ignored by Git, a config.toml file as a comprehensive configuration blueprint for managing various aspects of the Supabase environment, and updates to the environment variable declarations in .env.example, env.d.ts, and next.config.mjs to support integration with Supabase services.

Changes

File(s)	Change Summary
supabase/.gitignore	Added a .gitignore file to ignore .branches, .temp, and .env files.
supabase/config.toml	Introduced a config.toml file with sections for API, database, real-time features, authentication, storage, analytics, and experimental configurations, including numerous new parameters for customization.
supabase/.env.example, env.d.ts, next.config.mjs	Added SUPABASE_URL and SUPABASE_ANON_KEY environment variables to support Supabase integration.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Git
    participant Supabase

    Developer->>Git: Add .gitignore and config.toml
    Git->>Supabase: Ignore specified files
    Developer->>Supabase: Configure project settings
    Supabase-->>Developer: Apply configurations

Loading

🐇 In the garden where code does bloom,
A .gitignore clears the cluttered room.
With config.toml, settings align,
Supabase shines, oh how divine!
Hopping through changes, we cheer and play,
A brighter project, hip-hip-hooray! 🌼

Tip

Announcements

• The review status is no longer posted as a separate comment when there are no actionable or nitpick comments. In such cases, the review status is included in the walkthrough comment.
• We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.
• Possibly related PRs: Walkthrough comment now includes a list of potentially related PRs to help you recall past context. Please share any feedback in the discussion post on our Discord.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs in the walkthrough comment. You can also provide custom labeling instructions in the UI or configuration file.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b6ad5b9 and 7c28d72.

Files selected for processing (3)

• .env.example (1 hunks)
• env.d.ts (1 hunks)
• next.config.mjs (1 hunks)

Additional comments not posted (3)

.env.example (1)

5-6: LGTM!

The addition of the Supabase environment variables is approved.

Remember to replace the placeholders with actual values.

next.config.mjs (1)

5-6: LGTM!

The addition of the Supabase environment variables to the Next.js configuration is approved.

env.d.ts (1)

6-7: LGTM!

The addition of the Supabase environment variable type definitions is approved.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.