Migration error?

[guretalde]

When I launch the app for the first time with docker:
docker-compose up -d

i get the following error:

Attaching to airtrail, airtrail_db
airtrail    | Applying migrations...
airtrail    | Resolving dependencies
airtrail    | Resolved, downloaded and extracted [26]
airtrail    | Saved lockfile
airtrail    | Starting server...
airtrail    | Listening on 0.0.0.0:3000
airtrail    | 530 |         result = new this._Promise((resolve, reject) => {
airtrail    | 531 |           query.callback = (err, res) => (err ? reject(err) : resolve(res))
airtrail    | 532 |         }).catch((err) => {
airtrail    | 533 |           // replace the stack trace that leads to `TCP.onStreamRead` with one that leads back to the
airtrail    | 534 |           // application that created the query
airtrail    | 535 |           Error.captureStackTrace(err)
airtrail    |                       ^
airtrail    | error: relation "app_config" does not exist
airtrail    |  code: "42P01"
airtrail    | 
airtrail    |       at /app/node_modules/pg/lib/client.js:535:17
airtrail    |       at processTicksAndRejections (native:1:1)
airtrail    |       at /app/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:104:21

It says that the "app_config" relation does not exist. Maybe that the migrations didn't apply?

Thx in advance!

[Arcturuss]

yes, migrations did not apply. #71

[guretalde]

Fixed with the latest version.

I'm really sorry, I reviewed the issues but skipped the problem when I saw the subject indicated it was using Kubernetes.

Thanks for everything.

[johanohly]

I am glad to hear it!
And no worries, the issue probably should've been renamed when the real cause was found.

[johanohly]

Try again with the newest release. There is a potential fix for this included.