keystonejs / keystonejs/keystone

[railway-deployment]: The table `public.User` does not exist in the current database.

Open
#9,136 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
10k
Forks
1.3k
Avg merge
19h 14m
Merged PRs (30d)
19

Description

I successfully created a Keystone v6 project and added a custom field. Despite encountering some errors, I managed to deploy the project on railway app. Nevertheless, I am currently facing a database error from Prisma which needs to be resolved.

The project should just start and perform data migration or generation. It should not give me database errors

**The issue:**
![image](https://github.com/keystonejs/keystone/assets/56048741/9b8af8f1-b388-46f4-84c5-433a85b329ff)

**package.json**
![image](https://github.com/keystonejs/keystone/assets/56048741/a151c662-3de1-4fc7-8cc0-69a080cdce68)

I am using node v18

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Keystone v6 deployment on Railway with Node 18 and inspect the reported Prisma database error. The payload does not name any repository files or tests; done means the deployed project starts and completes its migration or generation without reporting that public.User is missing.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cloud, databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.