Remove obsolete Docker/Buildkite infra, update to Supabase-based local dev

.env.test

@@ -1,25 +1,25 @@
 NEXT_PUBLIC_BASE_URL=http://localhost:3000
-PGHOST=
-PGPORT=5432
-PGUSER=
+PGHOST=127.0.0.1
+PGPORT=54322
+PGUSER=postgres
 PGDATABASE=postgres
-PGPASSWORD=
+PGPASSWORD=postgres
 SENTRY_DSN=sentryDsn
 SENTRY_ENV=sentryEnv
 PUBLIC_S3_BASE_URL=https://test.example.com
-S3_ENDPOINT=
+S3_ENDPOINT=http://127.0.0.1:54321/storage/v1/s3
 S3_REGION=local
 S3_ACCESS_KEY_ID=accesskeyneedstobeexactly32chars
 S3_ACCESS_KEY_SECRET=12345678
 S3_MAPS_BUCKET=paradb-maps-test
-MEILISEARCH_HOST=https://
+MEILISEARCH_HOST=http://127.0.0.1:7700
 MEILISEARCH_KEY=123
 FLAGS_IMPLEMENTATION=local
 FLAGS_EDGE_CONFIG=
 FLAGS_EDGE_CONFIG_KEY=
-NEXT_PUBLIC_SUPABASE_URL=
-NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=
-SUPABASE_SECRET_KEY=
+NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
+NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
+SUPABASE_SECRET_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU
 AXIOM_API_TOKEN=
 AXIOM_DATASET=
 NEXT_PUBLIC_AXIOM_API_TOKEN=

AGENTS.md

@@ -5,7 +5,7 @@ Although you are taking on the persona of an intern developer, your skills are t
 
 This is a website that allows users to host custom maps and songs for a rhythm drumming game called "Paradiddle".
 Custom maps consist of a zip file, which contains a .rlrr metadata file along with the audio tracks for the song. The audio tracks can either be the song itself, or the audio stems of the song that can allow the game to play the song without any drum track (as the player will be drumming along themselves).
-The codebase uses Docker to run third-party services locally (Meilisearch for search, Minio for a local S3 instance), the local Supabase CLI for running the Supabase database locally, and the standad Next.js dev mode to run the backend and frontend locally.
+The codebase uses the local Supabase CLI for running the Supabase database locally (which includes Postgres and Auth), and the standard Next.js dev mode to run the backend and frontend locally. Meilisearch is used for search, and S3 (or MinIO locally) is used for blob storage.
 
 # Tech stack
 
@@ -36,9 +36,9 @@ The codebase uses Docker to run third-party services locally (Meilisearch for se
 
 # Commands
 
-- `bun dev` will start local services on Docker
+- `bun dev:local` will start Next.js in dev mode with local env
 - `bun supabase start` will start Supabase locally
-- `bun next dev` will run Next.js in dev mode
+- `bun test` will run the test suite
 - `bun format` will format the codebase with Prettier
 - `bun check` will typecheck and lint
 

README.md

@@ -6,19 +6,22 @@ git clone https://github.com/bitnimble/paradb.git
 cd paradb
 bun install
 
-# Install and start postgres
-sudo apt install postgresql
-sudo service postgresql start
+# Start local Supabase (requires Supabase CLI)
+bun supabase start
 
-# Create postgres user for yourself
-sudo -u postgres createuser --interactive --pwprompt
+# Copy the example env file and fill in any missing values
+cp .env.test .env.localdev
 
-# Edit .env to fill out your username and password!
+# Start the dev server
+bun dev:local
+```
+
+## Running tests
 
-# Create db and instantiate schema
-createdb paradb
-db/init.sh
+```
+# Ensure local Supabase is running
+bun supabase start
 
-# Start server
-bun dev
+# Run tests
+bun test
 ```

package.json

@@ -6,13 +6,11 @@
     "dev:local": "dotenv -e .env.localdev -- bun next dev",
     "dev:dev": "dotenv -e .env.dev -- bun next dev",
     "dev:prod": "dotenv -e .env.prod -- bun next dev",
-    "build": "sudo docker compose -f docker/docker-compose.yml --env-file .env build",
-    "start": "sudo docker compose -f docker/docker-compose.yml --env-file .env up --build",
     "check": "bun tsc && bun eslint .",
     "lint": "eslint .",
     "format": "prettier . --write",
     "schema": "tools/update_schema.sh",
-    "test": "sudo docker compose -f docker/docker-compose.test.yml --env-file .env.test up --build --abort-on-container-exit"
+    "test": "dotenv -e .env.test -- bun jest --runInBand"
   },
   "dependencies": {
     "@aws-sdk/client-s3": "^3.958.0",

src/services/jest_setup.ts

@@ -8,11 +8,11 @@ loadEnvConfig(projectDir);
 
 async function initTestData() {
   const { pool } = await getServerContext();
-  const initialDataSqlPath = path.resolve(__dirname, '../../db/fake_data.sql');
-  const initialDataSql = await fs.readFile(initialDataSqlPath).then((b) => b.toString());
+  const seedSqlPath = path.resolve(__dirname, '../../supabase/seed.sql');
+  const seedSql = await fs.readFile(seedSqlPath).then((b) => b.toString());
   await pool.query(`
 TRUNCATE maps, difficulties, users, favorites CASCADE;
-${initialDataSql}
+${seedSql}
 `);
 }
 

tools/update_schema.sh

@@ -4,6 +4,6 @@ set -euo pipefail
 
 HERE="$(realpath "${0}" | xargs dirname)"
 
-set -a; source "$HERE/../.env.docker"; set +a
+set -a; source "$HERE/../.env.localdev"; set +a
 bun zapatos
 bun supabase gen types typescript --local > "$HERE/../src/services/db/db.types.ts"