Is it possible to separate client and server wasp build?
each time I update stuff on client, and want to push to netlify, I need to run wasp build, but it rebuild both front and backend, it takes so much time(and sometime I only made change to client code, last second it could successfully build, but now it cannot find DATABASE_URL which is really weird), is it possible to only build front or back? and do we have a solution to integrate CI/CD? like I'm using coolify, let it automatically pull code from github when new code pushes triggered, so it can update automatically. @miho
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.