wasp db migrate-dev and wasp db studio not showing any output during installation of Open-SaaS
Sorry for asking such a basic question, I've been trying for a few days and can't figure out what I've done wrong.
I've followed the getting started page, successfully installed wasp etc, but when I get to the command
GPT-4 tells me I should see a prisma schema file created in the open-saas directory, but I don't see one.
Running on an M1 Air. Made sure to update Prisma to the latest version in case that was the issue.
Any help?
wasp db migrate-dev, I see no response from the terminal. Running wasp db studio likewise returns nothing. In docker I can see the volume wasp-dev-db-SaaSTemplate-1f16d4fc1d and a postgres image.GPT-4 tells me I should see a prisma schema file created in the open-saas directory, but I don't see one.
Running on an M1 Air. Made sure to update Prisma to the latest version in case that was the issue.
Any help?
9 Replies
Hmm. We will need some more info to help you. Are you in the correct project directory for open SaaS?
Make sure you’re running commands there.
You don’t need a prisma schema file. Wasp and the main.wasp file take care of that for you
GPT is lying a bit there heh, but on the other hand, you should be getting output from
wasp db studio and also from wasp db migrate-dev!
When you say you get no response -> is that virtually no response, like zero? Can you take a screenshot of it?
What happens if you run wasp info or wasp version? Those should give you simple, short output -> please screenshot and share their output.
You can also try running wasp compile, that should work and print a lot of output.Hey thanks for the responses and apologies for the nondescript message, I was a bit exasperated when I created the question! @Vinny (@Wasp) @martinsos . Upshot is I figured it out, thanks for the help! Still not sure what I did wrong per se, I followed the instructions to the best of my ability, opening a new tab where directed and navigating to the app/ directory inside open-saas. Running
wasp start db worked, but any subsequent wasp command was unresponsive, including version and compile.
I was finally able to get a response by closing the terminal, reopening and renavigating to the app/ directory and running the commands anew. Not sure why it didn't occur to me earlier! If it's of any use for someone having a similar issue going forward, I've attached a screen recording of what I was experiencing.Thanks for the video, this explains it!
So once you run
wasp start db, that terminal tab is occupied with the database running -> it is outputing its logs and stuff, but you can't really type anything, nobody is listening. This is not really connected to Wasp, it is just how it works when you run a long running process in a terminal. But I get why it can be confusing _> I actually wasn't expecting it to let you write anything, but it seems it does, however it goes nowhere.
So you really need to leave this tab running the db and go run commands in another tab, e.g. the first one.ah. it's not explicitly stated that you have to run those steps in a different terminal window in our docs. I'll change that now. Thanks for the heads up @cboRD
ok @cboRD @martinsos i've added more explicit instructions to our GETTING STARTED guide https://docs.opensaas.sh/start/getting-started/#start-your-db
OpenSaaS.sh
Getting Started
Open SaaS is a free, open-source, full-stack SaaS starter kit for React + NodeJS.
🙏
Awesome @Vinny (@Wasp) ! @cboRD thanks for reporting this and going with us through it!
That makes sense! Thanks for walking me through it 😅