WaspW
Wasp16mo ago
Conspyre

Building wasp apps: Easy. Deploying wasp apps: ?!@#$

I've tried deploying the back-end with 1) Docker 2) Node 3) "wasp start" reverse proxied behind Apache
None of those work. All behave the same way. I can access my routes (e.g. /api/test) and wasp provided routes (e.g. /api/auth/me /api/auth/email/signup) are 404.
I've given up on deploying on my server (it's just not possible) and am trying Railway

There is a step which says "Open the Settings and go to the Variables tab: click Variable reference and select DATABASE_URL (it will populate it with the correct value)"
We are setting the DATABASE_URL

This step does not auto-populate as suggested. If we do not populate the field, it remains empty.

If I go, in railway, to the postgres block, I can find a DATABASE_URL to copy, so I populate the server's DATABASE_URL with it.

When my server starts, it crashes, claiming not to have a DATABASE_URL:
------
Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Error validating datasource
db
: You must provide a nonempty URL. The environment variable DATABASE_URL resolved to an empty string.
--> schema.prisma:4
|
3 | provider = "postgresql"
4 | url = env("DATABASE_URL")
------
Looking at the DATABASE_URL, it appears to be populated with the values we copied from the Postgres block in Railway (e.g. postgresql://postgres:XXXXXX@postgres.railway.internal:5432/railway)

We are following the directions for Railway on https://wasp-lang.dev/docs/advanced/deployment/manually step by step, to the letter (have tried twice).

Please advise, over.
Was this page helpful?