The aim of this app is both to share great DJ mixes, and to show an example of how you can implement Wasp and Supabase together!
Wasp is used for the core client and server application.
Supabase is used for the database and storage.
- Copy the example server env file (required — most Wasp commands fail env validation without
.env.server):
cp .env.server.example .env.server-
Email for local login (important)
This repo defaults to Wasp’s
Dummyemail provider insrc/server/emailSender.wasp.ts. That is how local signup/login works without Resend:- No real email is sent.
- The verification / password-reset message (including the link) is printed in the
wasp startserver terminal. - Copy that link from the logs to finish verifying your account.
This is expected Wasp behaviour, not a bug: if
provideris"Resend", Wasp always calls Resend. It will not fall back to logging emails whenRESEND_API_KEYis missing or invalid — you get an API key error instead.For production (or if you want real emails locally), set a valid
RESEND_API_KEYin.env.serverand switch the provider:
// src/server/emailSender.wasp.ts
export const emailSender: EmailSender = {
provider: "Resend", // was "Dummy"
defaultFrom: {
name: "MixWasp",
email: "noreply@mixwasp.com", // must be allowed by your Resend domain
},
};- Run the database with
wasp start dband leave it running. - [OPTIONAL]: If this is the first time starting the app, or you've just made changes to your entities/prisma schema, also run
wasp db migrate-dev. - Run
wasp db seedand select all seed files to get some realistic data in the app to play with. - Run
wasp startand leave it running. This will install the app.
Feel free to contribute by selecting any issue and submitting a PR! If the feature/fix you want to include isn't already in the issues, please raise one before opening a PR. Thanks!