-
Notifications
You must be signed in to change notification settings - Fork 3
Adjust Shoppy migrations/seeding scripts for the new deployment approach. #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This reverts commit 97865d3.
@@ -1,4 +1,4 @@ | |||
PORT=4173 | |||
VITE_APP_METABASE_INSTANCE_URL=https://shoppy.hosted.staging.metabase.com | |||
VITE_APP_METABASE_INSTANCE_URL=https://shoppy.coredev.metabase.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When it is merged we still want to point the production app on Vercel to the old instance and switch to the new instance a bit later.
From what I see, we can do it via env vars on the Vercel
ALTER TABLE "people" ALTER COLUMN "shop_id" SET NOT NULL;--> statement-breakpoint | ||
DO $$ BEGIN | ||
ALTER TABLE "people" ADD CONSTRAINT "people_shop_id_shops_id_fk" FOREIGN KEY ("shop_id") REFERENCES "shops"("id") ON DELETE no action ON UPDATE no action; | ||
EXCEPTION | ||
WHEN duplicate_object THEN null; | ||
END $$; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we don't run migrations on Vercel automatically, we are ok with this change.
Adjust Shoppy migrations/seeding scripts for the new deployment approach.
How to verify: