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

Open
  • Is something wrong?
#186 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, python, supabase
Domain
authentication, databases, infrastructure

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
0
Forks
0
Avg merge
3h 33m
Merged PRs (30d)
50

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nfiasco/Quant-Time-Machine

All issues in nfiasco/Quant-Time-Machine

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.