Running migrations locally and remotely in Supabase - Step-by-Step Execution

Process Flow - Running migrations locally and remotely

Start Migration Process

↓

Choose Environment

↓

Local

↓

Run Migration

↓

Check Logs

↓

Success?

No→Fix Issues

Yes↓

End Migration

This flow shows choosing to run migrations either locally or remotely, executing them, checking logs, and handling success or errors.

Execution Sample

Supabase

supabase migration run --local
supabase migration run
supabase migration list

Commands to run migrations locally, then remotely, and check migration status.

Process Table

Step	Action	Environment	Result	Next Step
1	Start migration process	N/A	Ready to choose environment	Choose environment
2	Choose environment	Local	Selected local environment	Run migration locally
3	Run migration command	Local	Migration applied successfully	Check logs
4	Check logs	Local	No errors found	Success?
5	Success?	Local	Yes	End migration
6	Choose environment	Remote	Selected remote environment	Run migration remotely
7	Run migration command	Remote	Migration applied successfully	Check logs
8	Check logs	Remote	No errors found	Success?
9	Success?	Remote	Yes	End migration
10	End migration	N/A	Migration process complete	Process finished

💡 Migration process ends after successful migration on chosen environment.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 6	After Step 7	After Step 9	Final
Environment	None	Local	Local	Local	Remote	Remote	Remote	None
Migration Status	Not started	Not started	Success	Success	Not started	Success	Success	Complete
Logs	Empty	Empty	No errors	No errors	Empty	No errors	No errors	Reviewed

Key Moments - 3 Insights

Why do we check logs after running migrations?

Checking logs confirms if migrations applied correctly or if errors occurred, as shown in steps 4 and 8 in the execution table.

What happens if migration fails on remote environment?

If migration fails, logs will show errors and the process will move to fixing issues before retrying, which is implied after step 8 if success is No.

Can we run migrations locally and remotely in one command?

No, migrations must be run separately for local and remote environments, as shown by separate steps 3 and 7.

Visual Quiz - 3 Questions

Look at the execution table, what is the migration status after step 3?

A Success

B Not started

C Failed

D In progress

💡 Hint

Check the 'Migration Status' column after step 3 in the variable_tracker.

At which step does the process confirm migration success on the remote environment?

A Step 7

B Step 9

C Step 8

D Step 10

💡 Hint

Look at the 'Success?' action for the remote environment in the execution_table.

If logs showed errors after running migration locally, what would be the next step?

A End migration

B Run migration remotely

C Fix issues

D Check migration status

💡 Hint

Refer to the flow where 'Success?' is No leading to 'Fix Issues'.

Concept Snapshot

Running migrations means applying database changes.
Choose environment: local or remote.
Run migration command for chosen environment.
Check logs to confirm success or find errors.
Fix issues if migration fails, then retry.
Repeat for each environment as needed.

Full Transcript

This visual execution shows how to run database migrations using Supabase locally and remotely. First, you start the migration process and choose whether to run it locally or remotely. Then you run the migration command for that environment. After running, you check the logs to see if the migration succeeded or if there were errors. If successful, the process ends. If there are errors, you fix them before retrying. This process is repeated separately for local and remote environments to keep databases in sync.