Introduction

Next 15 starter kit based on Next.js, Auth.js and Prisma designed to accelerate the development of web-based (SaaS) applications.

Quickstart

Get started in about 30 minutes by following these steps.

Preparation

1. Unpack the Archive

2. Switch to the project's root directory

cd monorepo-next-prisma-authjs

2. Install PNPM if not already installed

npm i -g pnpm

3. Install the package dependencies of the whole monorepo

pnpm i

4. Copy the sample configurations

cp apps/dashboard/.env.example apps/dashboard/.env
cp apps/marketing/.env.example apps/marketing/.env
cp packages/database/.env.example packages/database/.env

Services

Database

Install PostgreSQL

1. Install PostgreSQL via Homebrew, Chocolatey or download it from the website.

brew install postgresql

2. Add an initial user.

sudo -u postgres psql
CREATE USER postgres WITH PASSWORD 'password';
ALTER USER postgres WITH SUPERUSER;
\q

3. Update database packages/database/.env with your credentials.

DATABASE_URL=postgresql://postgres:password@localhost:5432/database?schema=public

4. Apply the database migrations.

pnpm --filter database migrate dev

5. Update also the dashboard apps/dashboard/.env with your credentials.

DATABASE_URL=postgresql://postgres:password@localhost:5432/database?schema=public

Google Login (Optional)

1. Visit the Google Cloud Console.
2. Create an account if you don't have one already.
3. Navigate to APIs or click here
4. Configure the OAuth consent screen and add yourself as test user.
5. Click on Credentials, create new OAuth credentials and save those credentials.
6. Add the Authorized JavaScript origin to the credential settings.

http://localhost:3000

7. Add the Authorized redirect URI to the credential settings.

http://localhost:3000/api/auth/callback/google

8. Update dashboard apps/dashboard/.env with the created credentials.

AUTH_GOOGLE_CLIENT_ID=
AUTH_GOOGLE_CLIENT_SECRET=

Microsoft Login (Optional)

1. Visit the Azure Portal.
2. Create an account if you don't have one already.
3. Navigate to your Entra ID (Active Directory).
4. Register a new application with platform web.
5. Click on Authentication in the menu and add the redirect URIs

http://localhost:3000
http://localhost:3000/api/auth/callback/microsoft-entra-id

6. Under Certificates & Secrets, create a new client secret.
7. Update dashboard apps/dashboard/.env with the created secret.

AUTH_MICROSOFT_ENTRA_ID_CLIENT_ID=
AUTH_MICROSOFT_ENTRA_ID_CLIENT_SECRET=

Stripe

1. Visit the Stripe Dashboard.
2. Create an account if you don't have one already.
3. Activate test mode.
4. Activate the customer billing portal.
5. Create a product.
6. Create a price for the product.
7. Navigate to developer section and copy the API credentials.
8. Update dashboard apps/dashboard/.env with the IDs and credentials.

NEXT_PUBLIC_BILLING_STRIPE_PUBLISHABLE_KEY=
BILLING_STRIPE_SECRET_KEY=
BILLING_STRIPE_WEBHOOK_SECRET=
BILLING_PRO_PRODUCT_ID=
BILLING_PRO_PRODUCT_PRICE_ID=

SMTP Provider

The starter kit supports NodeMailer (SMTP) and Resend.

1. Choose an SMTP provider (Gmail for testing is fine).
2. Update dashboard apps/dashboard/.env with SMTP credentials.

EMAIL_FROM=
EMAIL_MAILER=NodeMailer # NodeMailer (default) | Resend

# NodeMailer

EMAIL_NODEMAILER_URL=

# Resend
EMAIL_RESEND_API_KEY=

For Gmail you need an app-specific password and set it up like this

EMAIL_NODEMAILER_URL=smtp://myemail@gmail.com:suyz yeba qtgv xrnp@smtp.gmail.com:465

SMTP provider is mandatory for credentials login.

Dashboard Application

1. Start the dashboard application

pnpm --filter dashboard dev

2. Navigate to http://localhost:3000

You’re all set to start!

Marketing Application

1. Start the marketing application

pnpm --filter marketing dev

2. Navigate to http://localhost:3001

You’re all set to start!

Troubleshoot

The generated Prisma types are not loaded.

Restart VS code (or the TS server).

It seems that I can't login

The database is probably not set up.

NPM throws an error

In v2 npm is no longer supported. It's all pnpm now. The problem is that npm, yarn and pnpm have different workspace syntax and package hoisting patterns, supporting all package managers is not possible in a monorepo setup.