S16.1: Spike: set up Supabase, migrations, and sign-in

未关闭
  • 哪里不对？
#186 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, python, supabase
领域
authentication, databases, infrastructure

调研方向

Start with supabase/config.toml and backend/app/config.py, then review the Supabase CLI setup and the linked roadmap entry for S16.1. Add the first migration, resolve the missing seed.sql reference, record the sign-in and token verification decision, update .env.example settings, and document local setup, migration workflow, and free plan limits in supabase/README.md. Done when the listed acceptance criteria are met and committed.

由索引模型根据 Issue 内容生成。

描述

area: infra priority: P1 spike

Roadmap story S16.1 · Project · Roadmap

Parent epic: E16 #108

Priority: P1 · Size: S · Sprint: 2 · Milestone: M2 · Area: infra · Depends on: — · Reqs: FR-U1, NFR-8 · Status: In progress

Story: As a team, we want the Supabase project and its workflow in place before we build on it, so that every schema change is reviewed and reproducible and nobody edits the database by hand.

Acceptance criteria

  • A hosted Supabase project (free plan) exists for development, and running Supabase locally (CLI plus Docker) is documented.
  • Schema changes are SQL migrations in supabase/migrations/, reviewed in pull requests like code. The seed.sql that supabase/config.toml points to exists, or the reference is removed.
  • The sign-in methods are chosen (for example, email and password, magic links, or GitHub), along with how the backend verifies Supabase's tokens. The decision is recorded (D9).
  • New settings are in the .env.example files: the project URL and public key for the frontend, and what the backend needs to verify tokens. The secret (service-role) key is used only on the server, if at all.
  • The free plan's limits are written down (500 MB, two active projects, paused after a week without activity), with a plan for demo days.

Tasks

  • Initialize the Supabase CLI configuration
  • Verify the hosted development project and team access in a committed setup record
  • Add the first migration and fix the missing seed.sql reference
  • Choose sign-in methods and token verification (D9)
  • Add account settings to .env.example and backend/app/config.py
  • Write supabase/README.md with migration workflow, local setup, and demo-day limits

Progress evidence (2026-11-08): Supabase CLI configuration is committed, but migrations and supabase/README.md are absent, seed.sql is referenced but missing, and auth methods/token verification remain undecided. A legacy market-data upload experiment does not implement accounts. Evidence: supabase/config.toml.

Audited against committed main at 0c32c57. Local, staged, and untracked work is excluded.

主要语言
Python
星标
0
派生
0
平均合并
3 小时 33 分钟
30 天内合并 PR
50

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nfiasco/Quant-Time-Machine 的其他 Issue

查看 nfiasco/Quant-Time-Machine 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。