Trying to initialise a production Postgres database on Railway for our backend service, but both Drizzle migration paths stall when pointed at the Railway DATABASE_PUBLIC_URL.

I'm trying to bootstrap the production schema using Drizzle from our backend workspace.

What I have already tried -

1. Railway pre-deploy command for Drizzle migrate

cd apps/backend && ./node_modules/.bin/drizzle-kit migrate --config=drizzle.config.ts

1. Running Drizzle migrate manually from the CLI against the Railway public Postgres URL

cd apps/backend

  SKIP_ENV_VALIDATION=true \

  DATABASE_URL='postgresql://postgres:<redacted>@junction.proxy.rlwy.net:32238/railway' \

  ./node_modules/.bin/drizzle-kit migrate --config=drizzle.config.ts

1. Running Drizzle push manually from the CLI against the same DATABASE_PUBLIC_URL

  cd apps/backend

  SKIP_ENV_VALIDATION=true \

  DATABASE_URL='postgresql://postgres:<redacted>@junction.proxy.rlwy.net:32238/railway' \

  ./node_modules/.bin/drizzle-kit push --config=drizzle.config.ts

Observed behaviour

For migrate, the command logs:

Reading config file '/Users/artivilla/dev/github.com/artivilla/outpaint-build/apps/backend/drizzle.config.ts'

  Using 'pg' driver for database querying

  [⣯] applying migrations...

and then stops / exits without creating tables.

For push, the command logs:

Reading config file '/Users/artivilla/dev/github.com/artivilla/outpaint-build/apps/backend/drizzle.config.ts'

  Using 'pg' driver for database querying

  [⣯] Pulling schema from database...

and then stops there.

In Railway deploy logs we also see the container reach Drizzle startup, then stop during the migration step.

Important confirmation

• There are currently no application tables in production.
• We have manually confirmed the production database is empty.
• So this does not appear to be a case where existing tables from an earlier drizzle-kit push are conflicting with migration files.

Additional CLI behaviour

Running railway connect postgres gives psql: error: connection to server at "junction.proxy.rlwy.net" (...), port 32238 failed: FATAL: password authentication failed for user "postgres"

Expected behaviour

• drizzle-kit migrate should apply the initial migration and create the schema, or
• drizzle-kit push should create the schema directly.

Actual behaviour

• Both commands begin database work, then hang / stop before any schema is created.
• No tables are created in production.