Help with DB build/deploy error.
Getting a weird build/deploy error when I try these commands. Haven't had this issue before and can't seem to find any docs/questions about it. Thanks!
source here: https://github.com/SoyMilkIsOk/terp-text
GitHub
GitHub - SoyMilkIsOk/terp-text
Contribute to SoyMilkIsOk/terp-text development by creating an account on GitHub.
10 Replies
https://wasp-lang.dev/docs/data-model/backends#connecting-to-an-existing-database Looking at these docs now!
Databases | Wasp
Entities, Operations and Automatic CRUD together make a high-level interface for working with your app's data. Still, all that data has to live somewhere, so let's see how Wasp deals with databases.
Still stuck unfortunately
Wohooo @SoyMilkIsOk, you just became a Waspeteer level 3!
Seemingly fixed this error by running the deploy/build command inline with my local DB env variable found in .wasp/out/server/.env ... command looked like:
seems a little hack-y though
Hey, if the error doesn't prevent you from deploying, you can safely ignore it.
That's a Prisma error while we are building the app for deployment, but it shouldn't matter if you set the env vars on Fly properly.
It wouldnt let me deploy after that error unfortunately, using the URL inline did fix the error. How would I go about setting env vars on Fly?
Env Variables | Wasp
Environment variables are used to configure projects based on the context in which they run. This allows them to exhibit different behaviors in different environments, such as development, staging, or production.
Deploying Manually | Wasp
We'll cover how to deploy your Wasp app manually to a variety of providers:
Here are some useful resources 😊
Thank you very much! I was stuck here (https://wasp-lang.dev/docs/advanced/deployment/cli#flyio) and didnt think to check the manually section
Deploying with the Wasp CLI | Wasp
Wasp CLI can deploy your full-stack application with only a single command.