Remove obsolete Docker/Buildkite infra, update to Supabase-based local dev by Copilot · Pull Request #60 · bitnimble/paradb

Copilot · 2026-02-09T06:37:56Z

Removes all obsolete Docker, Buildkite, and self-hosted infrastructure, replacing it with a Supabase CLI-based local development and test workflow.

Removed

Dockerfile, Dockerfile.dev, .dockerignore
docker/docker-compose.{yml,dev.yml,test.yml}
tools/docker/{start.sh,test.sh}
.buildkite/pipeline.yml

Updated

package.json — dropped Docker-based build/start scripts, test now runs dotenv -e .env.test -- bun jest --runInBand directly
jest_global_setup.ts — uses supabase db reset to apply migrations, schemas, and seeds once before the test suite
jest_setup.ts — uses TRUNCATE ... RESTART IDENTITY CASCADE + re-seed in beforeEach for fast per-test data reset
tools/update_schema.sh — sources .env.localdev instead of deleted .env.docker
.env.test — populated with Supabase local defaults, uses SEARCH_IMPLEMENTATION=postgres, Supabase keys left blank for users to supply from supabase status
README.md — rewritten for supabase start → bun dev:local workflow
AGENTS.md — updated repo summary and commands, removed Meilisearch and MinIO references

Added

.github/workflows/test.yml — CI workflow that sets up Bun and Supabase CLI, starts local Supabase, extracts keys from supabase status, and runs bun check + bun test

Original prompt

The repo infra has changed a lot, previously running a lot of things self hosted / manually, to now being hosted on Vercel and Supabase.

This means that a large part of the codebase around setup and testing is no longer working, e.g. it still has dockerfiles for running Postgres locally.

Update it so that:

all unused / no longer needed parts of Docker are removed

tests and test infra is updated to no longer rely on that

any readmes, initialisation or setup scripts, CI scripts, are updated accordingly

you can assume that the user has the Supabase CLI available locally for running a local version of Supabase

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

vercel · 2026-02-09T06:38:03Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
paradb	Ready	Preview, Comment	Feb 9, 2026 7:23am

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

bitnimble

Meilisearch is obsolete so don't reference it, don't delete it from the codebase though. If S3 can use the local Supabase S3 API, then Minio can be deleted.
Is there any way for this to avoid clobbering data in the local Supabase if the user has some? e.g. using a different schema in the PG database etc.

…test Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

Copilot · 2026-02-09T07:01:06Z

Meilisearch is obsolete so don't reference it, don't delete it from the codebase though. If S3 can use the local Supabase S3 API, then Minio can be deleted.
Is there any way for this to avoid clobberi...

Addressed in a3ff7f9 and c6e43c6:

Removed Meilisearch and MinIO from AGENTS.md, .env.test now uses SEARCH_IMPLEMENTATION=postgres
Tests use PGDATABASE=paradb_test so they won't clobber local dev data in the default postgres database
Added jest_global_setup.ts that creates paradb_test and applies the schema files before the test suite runs

declanvong

Also add or update Github workflows to run the tests, make sure the workflow environment is set up with Supabase

declanvong · 2026-02-09T07:10:07Z

src/services/jest_global_setup.ts

+  try {
+    const schemasDir = path.resolve(__dirname, '../../supabase/schemas');
+    // Apply schemas in order matching supabase config.toml
+    const schemaFiles = ['maps.sql', 'users.sql', 'favorites.sql', 'functions.sql', 'misc.sql'];


avoiding recreating the test db or manually applying schema changes in a TS file. if possible, run a shell script that uses the supabase db cli to create it

declanvong · 2026-02-09T07:10:34Z

src/services/jest_setup.ts

  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');


this needs to reset the DB as well as seed the data

declanvong · 2026-02-09T07:10:55Z

.env.test

-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


leave these keys out, they should be supplied by the user

bitnimble · 2026-02-09T07:15:23Z

@copilot address the changes recommended above

… workflow Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

Copilot · 2026-02-09T07:23:22Z

@copilot address the changes recommended above

Addressed in ec8f929..6186222:

jest_global_setup.ts: replaced manual DB creation + schema application with supabase db reset
jest_setup.ts: beforeEach now uses TRUNCATE ... RESTART IDENTITY CASCADE + re-seed (full schema reset handled once in global setup)
.env.test: removed hardcoded Supabase JWT keys, users supply them from supabase status
Added .github/workflows/test.yml CI workflow that sets up Supabase, extracts keys from supabase status, runs bun check and bun test

Initial plan

6ff0994

Copilot AI assigned Copilot and bitnimble Feb 9, 2026

Copilot started work on behalf of bitnimble February 9, 2026 06:38 View session

vercel bot deployed to Preview February 9, 2026 06:39 View deployment

chore: remove obsolete Docker/CI infra, update to Supabase-based setup

f19696f

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 06:44 View deployment

Copilot AI changed the title ~~[WIP] Update infra to remove unused Docker files and update tests~~ Remove obsolete Docker/Buildkite infra, update to Supabase-based local dev Feb 9, 2026

Copilot AI requested a review from bitnimble February 9, 2026 06:46

Copilot finished work on behalf of bitnimble February 9, 2026 06:46

bitnimble requested changes Feb 9, 2026

View reviewed changes

Copilot started work on behalf of bitnimble February 9, 2026 06:54 View session

chore: remove Meilisearch/MinIO from docs, isolate test DB to paradb_…

a3ff7f9

…test Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 06:58 View deployment

Copilot AI and others added 2 commits February 9, 2026 06:58

chore: harden jest_global_setup with env validation and error handling

88ab683

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

chore: use DatabaseError from pg-protocol for proper error typing

c6e43c6

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 07:00 View deployment

vercel bot deployed to Preview February 9, 2026 07:01 View deployment

Copilot AI requested a review from bitnimble February 9, 2026 07:01

Copilot finished work on behalf of bitnimble February 9, 2026 07:01

declanvong suggested changes Feb 9, 2026

View reviewed changes

Copilot started work on behalf of bitnimble February 9, 2026 07:15 View session

chore: use supabase db reset for tests, remove hardcoded keys, add CI…

ec8f929

… workflow Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 07:20 View deployment

chore: use truncate+reseed in beforeEach, fix CI env var parsing

0d593fb

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 07:22 View deployment

chore: add explicit permissions to CI workflow

6186222

Co-authored-by: bitnimble <4076797+bitnimble@users.noreply.github.com>

vercel bot deployed to Preview February 9, 2026 07:23 View deployment

Copilot finished work on behalf of bitnimble February 9, 2026 07:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

Remove obsolete Docker/Buildkite infra, update to Supabase-based local dev#60
Copilot wants to merge 8 commits intomainfrom
copilot/remove-dockerfiles-and-update-tests

Copilot AI commented Feb 9, 2026 •

edited

Loading

Uh oh!

vercel bot commented Feb 9, 2026 •

edited

Loading

Uh oh!

bitnimble left a comment

Uh oh!

Copilot AI commented Feb 9, 2026

Uh oh!

declanvong left a comment

Uh oh!

declanvong Feb 9, 2026

Uh oh!

declanvong Feb 9, 2026

Uh oh!

declanvong Feb 9, 2026

Uh oh!

bitnimble commented Feb 9, 2026

Uh oh!

Copilot AI commented Feb 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

Copilot AI commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Removed

Updated

Added

Uh oh!

vercel bot commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bitnimble left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Feb 9, 2026

Uh oh!

declanvong left a comment

Choose a reason for hiding this comment

Uh oh!

declanvong Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

declanvong Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

declanvong Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

bitnimble commented Feb 9, 2026

Uh oh!

Copilot AI commented Feb 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Feb 9, 2026 •

edited

Loading

vercel bot commented Feb 9, 2026 •

edited

Loading