agent-cto/freno-dev
1
0
Fork 0
forked from Mike/freno-dev
Code Pull Requests Activity

nessa: retire the API copy now served by nessa-api.freno.me

Browse Source 
The Nessa API (nessaDb.*, nessa.community.*, Clerk auth and the Clerk user
webhook) lives in the Nessa repo's server/ on pan. This copy never served
the app: RemoteAPIClient wraps every input in {"input": …}, which the stock
tRPC adapter here reads as the input itself (queries 404, writes no-op).
Clerk's webhook already targets nessa-api.freno.me.

Drops the routers, nessa-auth, the webhook, NessaConnectionFactory, the
NESSA_* env and the now-unused @clerk/backend and svix. Nessa's marketing,
privacy and deletion pages stay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Michael Freno
2026-10-13 13:54:14 -04:00
parent 9ff095a82c
commit 6898186df5
21 changed files with 12 additions and 5978 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
src/routes/nessa/privacy.tsx
View File

@@ -4,17 +4,16 @@
* Net-new privacy policy for the Nessa subdomain. Modeled on the Life and
* Lineage policy (the template for products with user accounts) but scoped to Nessa's real data practices:
*
* - Authentication: user accounts are managed by Clerk
* (`src/server/nessa-auth.ts` verifies Clerk session JWTs via the Clerk
* Backend JWKS endpoint). Nessa itself does not store passwords — Clerk is
* the identity provider.
* - Authentication: user accounts are managed by Clerk (the Nessa API server
* verifies Clerk session JWTs). Nessa itself does not store passwords —
* Clerk is the identity provider.
* - Community content: clubs, club challenges, club posts, post likes, and
* post comments (see `src/server/api/routers/nessa-community.ts`,
* `clubMemberships`, `clubChallenges`, `clubChallengeParticipations`,
* `clubPosts`, `clubPostLikes`, `clubPostComments`).
* - Storage: the Nessa data lives in a dedicated Turso (libSQL) database
* (`NessaConnectionFactory` in `src/server/db-connections.ts`), separate
* from the freno.me main DB and the Lineage DB.
* post comments (`clubMemberships`, `clubChallenges`,
* `clubChallengeParticipations`, `clubPosts`, `clubPostLikes`,
* `clubPostComments`).
* - Storage: the Nessa data lives in a dedicated Turso (libSQL) database,
* served by the Nessa API (`nessa-api.freno.me`, the Nessa repo's
* `server/`), separate from the freno.me main DB and the Lineage DB.
*
* PageHead is site-aware: only the base title is supplied; the
* ` | Nessa` suffix, `https://nessa.freno.me/privacy` canonical, and OG image