Deployment of 2.0.6 on Northflank #2352
-
Hi. Any help or pointers appreciated. I have been trying to deploy a 2.0.6 version of vendure on Northflank. I have had no problems deploying 1.9.3 using: https://github.com/vendure-ecommerce/one-click-deploy. However when I try and do the same with a 2.0.6 repo (created using It looks like there is an issue populating the database; I get the following logs, which suggest that the system is timing out creating the initial database schema: 2023-08-22T08:07:03.668022576Z stdout F [2023-08-22T08:07:03Z INFO ] Process terminated with exit code 0 [..bunch of additional table query errors] 2023-08-22T08:06:53.345656762Z stdout F QueryFailedError: relation "public.zone" does not exist 2023-08-22T08:06:53.332868861Z stdout F QueryFailedError: relation "public.administrator" does not exist [.. bunch of SQL commands for creating / altering vendure tables] 2023-08-22T08:06:11.267574453Z stdout F Your database schema does not match your current configuration. Generate a new migration for the following changes: When I look at the database that has been generated, all I see is:
I'm not sure if this is a timeout/race condition - perhaps the database isn't getting created as quickly as needed? I have tried different supported Postgres versions on Northflank, but I get the same issue. It would be great to get this working so any advice/help gratefully received! Incidentally the same repo works fine on my local machine using a local (dockerised) version of postgres. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi! To me this looks like it might be basically a race condition - the server and worker have some built-in logic where it will wait until the database schema is generated, see here. However, by default it will retry 20x at 100ms intervals, for a total of 2s. It looks like due to the low resources of the Northflank free tier, this schema creation step is taking too long and timing out. |
Beta Was this translation helpful? Give feedback.
Hi!
To me this looks like it might be basically a race condition - the server and worker have some built-in logic where it will wait until the database schema is generated, see here.
However, by default it will retry 20x at 100ms intervals, for a total of 2s. It looks like due to the low resources of the Northflank free tier, this schema creation step is taking too long and timing out.