Proposed AWS replatform closed without merging; work visible on the fork as a reference
saratpediredla-level5 opened a PR proposing a full platform swap for willchen96/mike - Supabase/Cloudflare out, AWS-native in - and it was closed eight seconds after it was opened. None of it landed on the upstream repo, but the design is preserved on the helix-tribune fork.
The proposed migration would have replaced every external dependency: Cloudflare Workers to CloudFront and Lambda via @opennextjs/aws, the Node backend to an ECS Fargate container with LibreOffice baked into the image, Supabase Postgres to Aurora Serverless v2 fronted by RDS Proxy, and Supabase Auth to Clerk. All infrastructure would have been described in a single SST v3 configuration covering VPC, RDS, S3, Fargate, the Next.js site, and secrets.
The data and auth layers would have been rewritten rather than wrapped. Drizzle ORM replacing @supabase/supabase-js at every callsite, with row-level security dropped in full and access checks moved into route handlers. user_id columns retyped from uuid to text for Clerk identifiers. The dropped handle_new_user trigger replaced by a first-request profile bootstrap in the auth middleware, cached in-process. R2 replaced by S3 using Fargate task-role credentials; Resend replaced by SES.
The PR description included a post-merge deployment checklist (SST secret population, SES identity verification, initial Drizzle migration via an RDS bastion, DNS cutover) and an upstream-fork strategy document identifying which paths would conflict on future merges from willchen96/mike - route handlers, auth middleware, storage lib, frontend auth files - and which would be conflict-free: infra, Dockerfile, SST config, and Drizzle schema.
Verification claimed zero TypeScript errors on both backend and frontend after the migration, with no remaining Supabase imports in either tree.
The PR closed immediately without review; the squash commit that actually landed this work is on helix-tribune's own branch (see the AWS migration post), not on upstream.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?