Make `supabase start` faster

Open
#361 4 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions

Research direction

Start from the GitHub Actions workflow shown in the issue, especially the setup-cli action and the supabase start and supabase status commands. Investigate whether the CLI or action supports caching that preserves the needed service role key; done means documenting a supported setup that measurably reduces startup time without losing the status output.

Written by the indexing model from the issue text.

Description

documentation

I'd like to make supabase start faster in my github actions CI. I'm running the following workflow in github actions:

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Setup Node.js 22
        uses: actions/setup-node@v4
        with:
          node-version: 22
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Setup Supabase
        uses: supabase/setup-cli@v1
        with:
          version: latest

      - name: Start Supabase
        run: supabase start

And the last step supabase start takes about 3min 30secs. I'm running supabase start (and not supabase db start) to be able to retrieve a service role key with supabase status afterwards.

Is it possible to somehow reduce the time it takes for this startup, with caching maybe? Has someone set this up properly already? Would be nice to add this to the documentation if so.

Dominant language
TypeScript
Stars
208
Forks
29
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.