Have you tried using the Railway CLI's SSH capabilities to run the command?

Or alternatively, a Supabase Template

No I don't, since I have no idea about any of the deployment, this is my first deployed project ever

I'll look for those, thanks Adam a lot

Would you tell me please how would I use Railway CLI

to migrate the prisma

Is the install guide at the top of the page not enough?

There are step by step instructions for both installation and using the SSH capabilities in the docs

Okay thanks

I did the following:

• installed the Railway CLI

• Connected the shell to my Railway account
  and then I did run npx prisma migrate deploy,
  It did show:

Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-ap-south-1.pooler.supabase.com:6543"

The shell like freezed, it didn't terminate, it just stayed there

I got a command from ChatGpt to check my DB connection is working: npx prisma db pull:
And also it did freeze on:

Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-ap-south-1.pooler.supabase.com:6543"

- Introspecting based on datasource defined in prisma/schema.prisma

They took too long so that I terminate them manually

One thing to note, I am now using only the Trial Plan

Sounds like your command went through, why did you terminate it?

It did took too long

I will try a solution provided by Gemini, it suggest to use
npx prisma migrate deploy && npm start:prod
at Custom Start Command,
I did use that before, but it didn't work,

What Gemini, suggest is that

the Supabase connection pooler URL (the one that uses port 6543) is optimized for running queries from your application but is not compatible with running migrations. Migrations require a direct, non-pooled connection to the database to alter the schema.
I'll try to apply that and see if it gonna workout

I didn't read carefully:
Look what already Supabase is saying:

# Direct connection to the database. Used for migrations
DIRECT_URL="postgresql://postgres.arphbeijateuxclzjosv:[YOUR-PASSWORD]@aws-0-ap-south-1.pooler.supabase.com:5432/postgres"

It is clear that the DIRECT_URL is used for MIGRATIONS

I'll test it, and I hope that it will work

Thanks Adam
I did fix finally, I was frustrated all the day,

The problem is that I only added Transaction pooler,
When I got faced with the two existed links, I thoughts I had to choose between them, so that I did choose Transaction pooler, but the other one is the one used for migrations,

I got other Errors, but what matter now is that the DB Table did created successfully

great! glad to hear it. Am I good to mark this thread as solved?

Yes, it is solved, thanks

!s