jason
WWasp
•Created by jason on 1/20/2025 in #đŸ™‹questions
Hosting a Wasp project?
Hi, I recently have created a webapp using Wasp. But the wasp docs are a little confusing with how hosting works. In my experience, when I've completed websites in the past, I just throw everything (frontend, backend, db) into docker containers and run it all off a cheap $4/month vps, or my own home server. I see most of the options require 2 different services, 1 for the frontend and a complete different service for the frontend and backend? Why is that? What's stopping us from just running everything off the same server? I'm a bit confused and would really appreciate someone explaining hosting to me.
5 replies
WWasp
•Created by jason on 1/6/2025 in #đŸ™‹questions
I messed up my db migrations...
Hi all.. I messed up my db migration and now I have no idea how to fix this. This 'migration' stuff is kind of insane, but I'm willing to put up with it because the framework itself is so solid.
Anyways, I have my OpenSaaS project being tracked by git. I was trying to implement a new feature, which included a change to the schema.prisma file, which required a db migration. However, I later decided to just roll back to the last git commit. This messed up my migration, the errors weren't specific at all about what I should do so I think I just removed the latest migration directory? It got super messed up, so I just reset the entire db using "wasp db reset".
It looked like it was working fine after reset. But now, I'm making more changes to the db schema, and tried migrating it. But it threw an error about the last migration from before I reset.
I tried, from the /app directory, running:
wasp clean
rm -rf .wasp/
rm -rf node_modules/
npm install
wasp db start
wasp db reset
But it's STILL talking about the old migration. Is it somewhere in my .git folder? What the hell is causing this headache?
12 replies