Multiple remote environments

Open
#143 7 comments 26 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
postgresql, typescript
Domain
cli, databases

Research direction

Start with the existing supabase db remote set and supabase db push command entry points. Trace how the single remote is stored and selected, then define the smallest consistent behavior for named remotes and a remote argument to db push; done means the example staging and production workflows work without breaking the current single-remote flow.

Written by the indexing model from the issue text.

Description

✨ Feature supabase/cli

Feature request

AO version 0.15.16

Currently one remote is allowed, set with

supabase db remote set <connection_string>

Could this be extended to support multiple environments?
ex (copying git):

supabase db remote add staging <connection_string>
# or
supabase db remote add production <connection_string>

with a selectable remote for supabase db push
ex:

supabase db push staging

?

Dominant language
TypeScript
Stars
2.4k
Forks
523
Avg merge
20h 47m
Merged PRs (30d)
243

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.

More from supabase/cli

All issues in supabase/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.