Deploying Wasp on Railway using SupaBase
Hey everyone. I have fully built my saas app using the open saas template and now was to deploy it using Railway. I am having a hard time getting it to deploy successfully. Has anyone else launch on Railway with SupaBase ? Thanks in advance
Currently the error I am getting in Railway after deploying is :
Starting Container
══ Env vars validation failed ══
- Required
════════════════════════════════
file:///app/.wasp/out/sdk/wasp/dist/env/validation.js:16
throw new Error('Error parsing environment variables');
^
Error: Error parsing environment variables
at ensureEnvSchema (file:///app/.wasp/out/sdk/wasp/dist/env/validation.js:16:19)
at file:///app/.wasp/out/sdk/wasp/dist/client/env.js:13:20
at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:337:24)
at async loadESM (node:internal/process/esm_loader:34:7)
at async handleMainPromise (node:internal/modules/run_main:106:12)
Node.js v18.20.7
2 Replies
Hi @Joc. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I apologize, but the provided knowledge sources don't contain specific information about deploying a Wasp app on Railway using Supabase. The sources mainly cover deploying Wasp apps on Railway using PostgreSQL, but don't mention Supabase integration.
However, I can provide some general guidance based on the available information:
1. Wasp supports deploying to Railway, but the process described in the documentation assumes you're using PostgreSQL directly on Railway, not Supabase.
2. The deployment process for Railway generally involves:
- Building your Wasp app
- Deploying the server
- Deploying the client
- Setting up environment variables
3. You might need to adjust the deployment process to work with Supabase instead of a direct PostgreSQL database on Railway.
4. Make sure you have the correct environment variables set up for Supabase connection in your Railway project.
5. You may need to modify the
DATABASE_URL environment variable to point to your Supabase database instead of a Railway-provisioned PostgreSQL database.
For more detailed instructions on deploying to Railway (without Supabase), you can refer to the Wasp documentation on manual deployment to Railway. However, keep in mind that you'll need to adapt these instructions for your Supabase setup.
If you continue to face issues, you might want to reach out to the Wasp community on their Discord channel or open an issue on their GitHub repository for more specific help with Supabase integration on Railway.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Joc, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hey @Joc
Hm, something seems to be missing in this message.
Can you please tell me the exact steps you've done, and then we'll try to figure it out.