27 lines
1.1 KiB
Markdown
Executable File
27 lines
1.1 KiB
Markdown
Executable File
# VYNDR — Blockers
|
|
|
|
## BLOCKER-001: Hosting Decision
|
|
**Status:** OPEN
|
|
**Impact:** Blocks deployment (Phase 3)
|
|
**Options:**
|
|
- Vercel — free tier, great for Next.js, limited backend
|
|
- Railway — better for full-stack, Node.js native, $5/mo start
|
|
**Decision needed by:** End of Phase 1
|
|
**Owner:** Kev
|
|
|
|
## BLOCKER-002: Auth Provider
|
|
**Status:** RESOLVED (2026-03-21)
|
|
**Decision:** Supabase Auth. See DECISION-004.
|
|
|
|
## BLOCKER-003: WSL2 Cannot Resolve *.supabase.co Domains
|
|
**Status:** OPEN
|
|
**Impact:** Blocks applying Feature 1.4 migration and running verify-schema.js from CLI
|
|
**Details:**
|
|
- WSL2 DNS resolver (10.255.255.254) cannot resolve `*.supabase.co` TLD
|
|
- Google DNS (8.8.8.8) returns NXDOMAIN — may be a new project with DNS propagation delay
|
|
- `*.supabase.com` (e.g., pooler, api) resolves fine
|
|
- Migration SQL is written and validated (37 tests pass)
|
|
**Workaround:** Apply migration via Supabase Dashboard SQL Editor
|
|
**Resolution path:** Either DNS propagates, or add Supabase IP to /etc/hosts, or use `supabase link` with access token via api.supabase.com
|
|
**Owner:** Kev
|