How to Build App with Next.js, Prisma, and Docker: A Developer Guide

In today's fast-paced development landscape, building robust and scalable web applications requires a powerful tech stack. Next.js, Prisma, and Docker are three essential tools that can help you achieve this goal.

In this blog, we’ll explore how to build, integrate, and deploy a powerful web application using Next.js, Prisma, and Docker. By combining Next.js for the frontend, Prisma as an efficient database management layer, and Docker for seamless containerization, we can create a scalable and production-ready application.

We’ll walk through setting up each component, configuring a multi-stage Docker build for optimized deployment, and managing services with Docker Compose.

How to Set Up a Next.js Project with Prisma and Docker?

Overview of Next.js, Prisma, and Docker

Next.js, Prisma, and Docker are a powerful combination for building and deploying modern web applications. Each tool plays a critical role in the stack:

1. Next.js is a React-based framework that provides server-side rendering and other optimizations, making it ideal for dynamic applications.

2. Prisma simplifies database management by acting as an ORM (Object Relational Mapper), allowing you to write clean, type-safe code to manage your database interactions. Prisma integrates well with PostgreSQL, MySQL, and other databases, making it flexible and scalable.

3. Docker is a containerization tool that encapsulates your entire app (including dependencies and environment configurations) into portable containers. This is especially useful for creating consistent development, testing, and production environments.

Together, Next.js, Prisma, and Docker form a solid foundation for building and deploying scalable applications that are both developer-friendly and highly adaptable.

How Next.js, Prisma, and Docker Work Together

• Next.js as the frontend: Next.js handles the frontend of your app, serving pages dynamically. By using the app directory in Next.js, you can organize your components, API routes, and utility functions in a logical structure.

• Prisma as the database layer: Prisma manages the database schema, data modeling, and interactions with the database. It allows you to work with data seamlessly by defining models in the prisma schema file, then generating the Prisma client, which lets you run queries directly from your Next.js app.

• Docker for containerization: Docker simplifies deployment by packaging your entire Next.js app, Prisma schema file, and database configuration into a Docker container. This ensures consistency across various environments and helps avoid compatibility issues. You can further configure multiple services using docker compose, allowing you to set up containers for the frontend, backend, and database components.

By combining these technologies, you can create a scalable and maintainable web app. In the following sections, you’ll learn how to install and configure each component step-by-step, from creating a new Next.js project to setting up Docker containers for seamless deployment.

Setting Up and Configuring Next.js

1. Create a New Next.js Project: Begin by initializing your Next.js app. You can do this easily by running the create next app command:

This command sets up the app directory, containing essential files and folders. Once created, navigate to your project folder:

2. Configure the Environment Variables: Next.js and Prisma rely heavily on environment variables, which you’ll define in an env file. This includes sensitive information like your database connection string. Create a new env file, and make sure you add it to the gitignore file to prevent it from being pushed to your git repository.

This connects your app to the database using the datasource db in Prisma.

Installing and Configuring Next.js

Creating a New Next.js Application

To get started with Next.js, you first need to initialize a new project. This can be done easily with the create next app command. This command sets up a basic Next.js application with all the essential configurations and folder structures in place, allowing you to dive into development right away.

Run the following command in your terminal:

This command will create a new folder, my-nextjs-app, containing all the files and configurations required for a Next.js app. Once the app is created, you can navigate to this folder:

Essential Next.js Folder Structure and Files

The new app directory includes the following key folders and files:

• pages/: The primary location for page components. Each file here automatically maps to a route in your app.

• public/: Stores static files like images and other assets.

• styles/: Houses CSS files, such as global styles and module-based styles.

• next.config.js: Contains custom configurations for the Next.js app.

• package.json: Lists all dependencies and scripts for running and building the app.

This structure provides an efficient way to manage your application files. Additionally, with Next.js 13 and later, you may use the app directory, which introduces a more streamlined way of managing routes and components, especially in larger applications.

Setting Up Environment Variables

Importance of Environment Variables

Environment variables are essential in any application for securely storing sensitive information such as API keys, database connection strings, and other configuration values. In a Next.js and Prisma project, environment variables help you manage the connection to your database, API configurations, and other settings that vary between development and production environments.

By convention, these variables are stored in an env file located at the root of your project. This file is then referenced by both Next.js and Prisma. Since it contains sensitive information, make sure to add it to your gitignore file to prevent accidental exposure when pushing your code to a git repository.

Configuring Environment Variables for Next.js and Prisma

1. Create an env file: Start by creating a new file called .env.local in the root directory of your Next.js project. This file will hold your environment variables for the local development environment.

2. Add Database Connection URL: In the env file, specify the for Prisma to connect to your database. This will be used as the datasource db in your Prisma configuration.

Here, replace username, password, localhost, and mydatabase with the details specific to your database. If you’re using Docker, you can define the hostname as the postgres container name specified in docker compose.

3. Use Environment Variables in Prisma: In your Prisma configuration, you’ll refer to this variable in your prisma schema file. When you run the npx prisma generate or npx prisma migrate dev commands, Prisma will automatically reference the database specified in your env file.

4. Adding Additional Environment Variables: If your Next.js app requires other environment variables (e.g., for an API key), you can add them to this same env file.

Accessing Environment Variables in Next.js

In Next.js, you can access these variables directly using the process.env object:

In this setup, Next.js will load the environment variables securely, allowing you to reference your database or other configurations seamlessly throughout your app.

Integrating Prisma with Next.js

Setting Up Prisma for Database Management

Prisma is a powerful tool that simplifies database management by providing an ORM (Object Relational Mapper) for efficient interaction with your database. To start integrating Prisma with your Next.js project, follow these steps:

Installing Prisma and Initializing the Schema

1. Install Prisma and the Prisma Client: Start by installing Prisma in your Next.js project. Prisma Client is necessary to interact with the database from within your app.

2. Initialize Prisma: After installation, initialize Prisma using the npx prisma init command. This command will create a new Prisma directory, including a prisma schema file (schema.prisma) and a new env file for database configuration.

After running this command, you’ll see a new folder named prisma and an env file at the root of your project.

Choosing a Database and Connecting with Prisma

In your env file, specify the for connecting Prisma to your database. Prisma supports databases like PostgreSQL, MySQL, SQLite, and others. Here’s an example connection string for PostgreSQL:

Replace username, password, localhost , and mydatabase with the details specific to your database setup. In the prisma schema file, configure Prisma to use this database as its datasource db.

This setup allows Prisma to connect to the specified database and begin managing it. With this setup, Prisma will pull connection details directly from your env file, helping secure your application by keeping sensitive information out of your codebase.

Creating and Managing Database Models

With Prisma, you define your database schema in the prisma schema file using a simple syntax that Prisma will translate into database tables and columns.

Defining Models in the Prisma Schema

In the schema.prisma file, you define models to represent the structure of your data. For example, if you want a User model, you might define it like this:

Each model represents a database table, with each property corresponding to a column. The above User model includes fields for id, name, email, and createdAt. The @id and @default(autoincrement()) annotations configure Prisma to use an auto-incremented integer as the primary key.

Running Migrations to Sync Database with Models

Once you’ve defined your models in the prisma schema file, you’ll need to create and apply migrations to sync your database with the new model structure.

1. Generate Migration Files: Use the following command to create a new migration based on your model definitions:

This command will create a new folder with migration SQL files in the Prisma directory. These files define the SQL commands to set up the database schema based on your Prisma models.

2. Apply Migrations: The migrate dev command will also apply the migration to your database. Each time you modify your models, rerun this command to keep the database in sync.

Using Prisma Client in Your Application

After defining models and running migrations, Prisma generates a type-safe Prisma Client for accessing your database. You can import and use this client throughout your Next.js app to perform database operations.

To regenerate Prisma Client, run:

You can now import Prisma Client in your Next.js API routes or server-side functions. Here’s an example of querying the User table in an API route:

This handler retrieves all User entries from the database and sends them in the response. The Prisma Client provides an easy-to-use API for running complex SQL queries without needing to write raw SQL.

Dockerizing the Next.js and Prisma Application

Writing the Dockerfile for Next.js and Prisma

Dockerizing your Next.js and Prisma application makes it easy to deploy and manage by encapsulating the entire setup within a container. For this, you’ll create a multi-stage Dockerfile to optimize the build and separate dependencies for the development and production environments.

Setting Up a Multi-Stage Dockerfile for Optimized Build

A multi-stage Dockerfile allows you to reduce the image size by splitting the build process into distinct stages. Here’s an example Dockerfile for a Next.js and Prisma application:

This Dockerfile does the following:

1. Install dependencies: The first stage (builder) installs all the required dependencies and builds the Next.js application.

2. Copy only necessary files: The second stage (production image) copies only essential files (like the .next build folder and ) to keep the final Docker image slim and optimized.

3. Expose and run the app: Exposes port 3000 for the app to run and starts the application.

Including Prisma and Environment Variables in Docker Configuration

Prisma relies on environment variables (such as the ) to connect to the database. Add these variables in an env file or directly within the Dockerfile. Additionally, you may need to install the Prisma CLI in the builder stage to handle migrations and schema generation.

To ensure Prisma works in the Docker environment, add to your env file and ensure it points to the database service in your Docker Compose setup.

Creating a Docker Compose File

Docker Compose allows you to define and manage multiple containers (services) in a single configuration file, which is particularly useful when running Next.js, Prisma, and your database as separate containers.

Setting Up Services for Next.js, Prisma, and Database

1. Create a Docker Compose File: In the root of your project, create a docker-compose.yml file with the following setup:

In this setup:

• The db service runs PostgreSQL as the database. It’s configured with the environment variables , , and for database setup and uses a named volume () to persist data.

• The app service builds the Dockerfile we created for Next.js. The points to the db service for database access. Ports are mapped to expose the application on port 3000, and the service depends on db to ensure the database is available when the app starts.

Configuring Network and Dependencies between Services

Docker Compose allows you to manage the network configuration between containers. In the above file:

• Networks: Both services are assigned to the app-network, ensuring they can communicate.

• Dependencies: The configuration ensures the database service starts before the Next.js application.

Running Docker Compose

To start all the services, simply use:

This command builds and starts each container according to the configuration in the docker-compose.yml file. You should see logs from both the database and the Next.js application in the terminal.

Deploying the Dockerized Application

Building and Running Docker Containers

Building and Running the Application with Docker Commands

After setting up the Dockerfile and Docker Compose configurations, you’re ready to build and run your containerized Next.js and Prisma application. Here’s how to get started:

1. Build the Docker Images: First, ensure you’re in the root directory of your project where the Dockerfile and docker-compose.yml are located. Use the following command to build the images:

This command will process the Dockerfile for each service and create images for both the Next.js app (app service) and the database (db service).

2. Run the Containers: Once the images are built, start the containers with the following command:

This will launch both the app and db containers. The Next.js app should now be running and accessible via http://localhost:3000 , while the database service will be accessible internally within the container network.

Common Issues and Troubleshooting Tips for Containerized Apps

When deploying a containerized Next.js and Prisma application, there are common issues you may encounter. Here are some troubleshooting tips:

• Database Connection Issues: Ensure that your environment variable in the env file or docker-compose.yml is correctly set. If you’re using a postgres container, make sure the db service is referenced correctly in the URL (postgres://postgres:postgres@db:5432/mydatabase).

• Prisma Client Not Found: If Prisma Client is not generated, make sure to run npx prisma generate either as part of the Dockerfile or manually within the container after running docker-compose up. You can use an exec command to run npx prisma generate in the running container:

• Outdated Migrations: If you make changes to the Prisma schema file, you’ll need to rerun migrations. Use:

• File Permissions Errors: Sometimes Docker containers, especially those using the alpine version, may have file permission issues. You can resolve this by ensuring the correct permissions on your and other key directories in the Dockerfile.

Finalizing Deployment with Docker Compose

Preparing Docker Compose for Production

To optimize your Docker Compose setup for a production environment, a few changes are recommended:

1. Set Environment to Production: Ensure that the environment variable is set to production for your app service. This disables Next.js dev features that aren’t needed in production and optimizes performance.

2. Minimize Image Size: You might consider using a smaller base image, like node:16-alpine, in the Dockerfile to reduce the size of the final container. Additionally, remove any dev dependencies and only copy what’s necessary for production.

3. Handle Static Files: If your app includes a lot of static assets, consider using a CDN to serve those files in production rather than hosting them within the Docker container.

Testing the Deployment and Ensuring Database Connections

Once configured for production, it’s crucial to test the deployment. Here are some tips to verify everything is working correctly:

1. Run Docker Compose in Detached Mode: To start the containers in the background, use the d flag with the up command:

This will keep the services running in the background, allowing you to continue working or inspect logs as needed.

2. Check Container Logs: Use the following command to view logs and ensure there are no errors related to database connections, migrations, or the app itself:

3. Test Database Connections: You can verify the Prisma connection to the database by using Prisma Studio to view your data in the database. Run:

This opens a UI in your browser where you can inspect and manipulate data.

4. Health Checks and Scaling: For production, you may add health checks to your Docker Compose setup to monitor the status of each service. Additionally, you might want to consider adding replicas of the app service to handle higher traffic loads, which can be managed with a load balancer outside Docker Compose.

The Bottom Line!

In conclusion, this article provided a step-by-step guide on building and deploying a robust application with Next.js, Prisma, and Docker. By setting up Next.js as the frontend framework, Prisma for seamless database management, and Docker for containerized deployment, we created a streamlined, scalable, and production-ready app. We covered configuring a multi-stage Docker build, managing services with Docker Compose, and ensuring secure and efficient database connections. The main takeaway is that using Next.js, Prisma, and Docker together allows for a modern, scalable approach to web development, making it easy to deploy and maintain applications across environments.

npx create-next-app my-nextjs-prisma-docker-app

cd my-nextjs-prisma-docker-app

DATABASE_URL=postgresql://username:password@localhost:5432/mydatabase

npx create-next-app my-nextjs-app

cd my-nextjs-app

DATABASE_URL="postgresql://username:password@localhost:5432/mydatabase"

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

export default function HomePage() {
  console.log(process.env.DATABASE_URL); // Example usage
  return <h1>Welcome to My Next.js App</h1>;
}

npm install prisma @prisma/client

npx prisma init

DATABASE_URL="postgresql://username:password@localhost:5432/mydatabase"

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id       Int      @id @default(autoincrement())
  name     String
  email    String   @unique
  createdAt DateTime @default(now())
}

npx prisma migrate dev --name init

npx prisma generate

// pages/api/users.js
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

export default async function handler(req, res) {
  const users = await prisma.user.findMany(); // Fetch all users
  res.json(users);
}

# Stage 1: Install dependencies and build the application
FROM node:16 AS builder

# Set working directory
WORKDIR /app

# Copy package.json and package-lock.json
COPY package.json package-lock.json ./

# Install dependencies
RUN npm install

# Copy all source code into the container
COPY . .

# Build the Next.js application
RUN npm run build

# Stage 2: Production image
FROM node:16-alpine AS production

# Set working directory
WORKDIR /app

# Copy only the necessary files from the build stage
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/package.json ./

# Expose the port that the app will run on
EXPOSE 3000

# Start the application
CMD ["npm", "start"]

version: '3.8'

services:
  # Database service (e.g., PostgreSQL)
  db:
    image: postgres:13
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: mydatabase
    volumes:
      - db_data:/var/lib/postgresql/data
    networks:
      - app-network

  # Prisma service (Next.js application)
  app:
    build:
      context: .
      dockerfile: Dockerfile
    environment:
      DATABASE_URL: postgres://postgres:postgres@db:5432/mydatabase
      NODE_ENV: production
    ports:
      - "3000:3000"
    depends_on:
      - db
    networks:
      - app-network

volumes:
  db_data:

networks:
  app-network:

docker-compose up --build

docker-compose build

docker-compose up

docker-compose exec app npx prisma generate

docker-compose exec app npx prisma migrate dev

environment:
  DATABASE_URL: postgres://postgres:postgres@db:5432/mydatabase
  NODE_ENV: production

docker-compose up -d

docker-compose logs -f

docker-compose exec app npx prisma studio