Last active
March 20, 2023 23:49
-
-
Save jkcorrea/288b9f9cd833dfc73e8cb1adb64ab416 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# This script clones a supabase database without the data & owned by the current user | |
# Usage: clone_supabase_db.sh <new_db_name> [supabase_db_port] | |
# | |
# NOTE: [supabase_db_port] is optional and defaults to '54322' | |
# NOTE: You may seem some errors in the console. most of the time they are harmless for the purposes of running a test/shadow db. | |
# As long as you get a new DB with the same schema, you should be good to go. | |
# create a temp file to store the dump | |
TMP_DIR=$(mktemp -d) | |
if [ $? -ne 0 ]; then | |
echo "$0: Can't create temp dir. Is \"mktemp\" installed?" | |
exit 1 | |
fi | |
DUMP_FILE="${TMP_DIR}"/db.dump | |
# dump schema only from supabase's db | |
pg_dump -Fc --schema-only --no-acl postgresql://postgres:postgres@localhost:${2:-54322}/postgres > ${DUMP_FILE} | |
# (re)create the database | |
dropdb "$1" | |
createdb "$1" | |
# restore the schema | |
pg_restore --create --clean --if-exists --no-owner -d "$1" ${DUMP_FILE} | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes I create custom Prisma migrations that refer to supabase-specific things (auth, storage, etc).
Your shadow db probably doesn't have these schemas, so Prisma Migrate will complain when running those migrations.
This script clones only the schema from your supabase db into a new db (which you name as the first arg)!