[Epic] Service and data foundation #1

New issue

Closed

opened 2026-06-12 20:26:36 +00:00 by james · 0 comments

james commented

2026-06-12 20:26:36 +00:00

Owner

The Next.js + TypeScript backbone the rest of the app sits on. By the end of this epic:

A containerized Next.js service exists and runs.
All data access goes through a DB abstraction with parity on SQLite and Postgres.
Migrations are automated.
/api/health is the only unauthenticated endpoint; everything else requires a valid session.
Local users and OAuth2 users can sign in; the two identity types can be linked to one account.
Multiple users can register on a single instance; every user's data is isolated at the DB layer by user_id.

Linked tickets

Scaffold Next.js + TypeScript service
Database abstraction with SQLite + Postgres + dual-engine test harness
Containerize service + unauthenticated /api/health endpoint
Authorization middleware
Local user authentication
OAuth2 authentication + account linking

Exit criteria

A self-hoster can docker run the service against either DB engine, register an account locally or via OAuth2, and reach an authorized endpoint with a valid session.
Two users registered on the same instance see only their own data; cross-user reads return 404.

The Next.js + TypeScript backbone the rest of the app sits on. By the end of this epic: - A containerized Next.js service exists and runs. - All data access goes through a DB abstraction with parity on SQLite and Postgres. - Migrations are automated. - `/api/health` is the only unauthenticated endpoint; everything else requires a valid session. - Local users and OAuth2 users can sign in; the two identity types can be linked to one account. - **Multiple users can register on a single instance; every user's data is isolated at the DB layer by `user_id`.** ## Linked tickets - Scaffold Next.js + TypeScript service - Database abstraction with SQLite + Postgres + dual-engine test harness - Containerize service + unauthenticated `/api/health` endpoint - Authorization middleware - Local user authentication - OAuth2 authentication + account linking ## Exit criteria - A self-hoster can `docker run` the service against either DB engine, register an account locally or via OAuth2, and reach an authorized endpoint with a valid session. - **Two users registered on the same instance see only their own data; cross-user reads return 404.**

james referenced this issue

2026-06-12 20:27:06 +00:00

Scaffold Next.js + TypeScript service #7

james referenced this issue

2026-06-12 20:27:12 +00:00

Database abstraction with SQLite + Postgres parity #8

james referenced this issue

2026-06-12 20:27:17 +00:00

Containerize service + unauthenticated /api/health endpoint #9

james referenced this issue

2026-06-12 20:27:21 +00:00

Authorization middleware #10