Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -236,6 +236,19 @@ npm run db:seed

---

## πŸ”Œ Supabase Integration

This project uses Supabase for external data access and future integrations.

Update your `.env` file with:

```bash
SUPABASE_URL=...
SUPABASE_ANON_KEY=...
```
Comment on lines +289 to +298
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ’‘ Verification agent

🧩 Analysis chain

Verify variables are used in code and present in sample envs

Ensure the code expects these exact names and that .env.example/.env.test include them.


🏁 Script executed:

#!/bin/bash
# Find references to Supabase env vars across the repo
rg -nP '\bSUPABASE_(URL|ANON_KEY|SERVICE_ROLE_KEY)\b' -C2

# Confirm they exist in sample env files
fd -H '^\.env(\.example|\.test)?$' -a | xargs -I{} sh -c 'echo "---- {}"; cat "{}" | rg -n "SUPABASE_" || true'

# Check docker compose files for propagation
fd -a 'docker-compose*.yml' | xargs -I{} sh -c 'echo "---- {}"; rg -n "SUPABASE_" "{}" || true'

Length of output: 1122


Add missing Supabase env vars to sample env files

  • .env.test is currently missing SUPABASE_URL and SUPABASE_ANON_KEY which are required by src/config/supabase.ts; add them with appropriate test placeholders.
  • Confirm docker-compose.yml propagates these vars to any Supabase‐dependent services (via env_file or environment).
🧰 Tools
πŸͺ› LanguageTool

[grammar] ~239-~239: There might be a mistake here.
Context: ...eed ``` --- ## πŸ”Œ Supabase Integration This project uses Supabase for external ...

(QB_NEW_EN)


Comment on lines +289 to +299
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ› οΈ Refactor suggestion

⚠️ Potential issue

Avoid README/readme duplication (case conflict).

Both README.md and readme.md exist; this breaks clones on case-insensitive FS (macOS/Windows) and confuses links. Keep a single README.md.

🧰 Tools
πŸͺ› LanguageTool

[grammar] ~289-~289: There might be a mistake here.
Context: ...eed ``` --- ## πŸ”Œ Supabase Integration This project uses Supabase for external ...

(QB_NEW_EN)

πŸ€– Prompt for AI Agents
In README.md around lines 289–299 there is a duplicate lower-case readme
(readme.md) in the repo which causes conflicts on case-insensitive filesystems;
consolidate content into a single README.md, remove or rename the redundant
readme.md from the repository, update any internal links or references to point
to README.md, and commit the change with a proper repo-case fix sequence so the
filename case change is recorded on case-insensitive systems.

---

## πŸ“ Module Overview

### Core Modules
Expand Down