It works as expected in the dev enviroment (next dev)

do you have npx prisma generate in dockerfile

here's the docker log

2023-11-16 21:21:52 Environment variables loaded from .env
2023-11-16 21:21:52 Prisma schema loaded from prisma/schema.prisma
2023-11-16 21:21:52 Datasource "db": SQLite database "dev.db" at "file:./dev.db"
2023-11-16 21:21:52 
2023-11-16 21:21:52 1 migration found in prisma/migrations
2023-11-16 21:21:52 
2023-11-16 21:21:52 
2023-11-16 21:21:52 No pending migrations to apply.
2023-11-16 21:21:52    â–² Next.js 14.0.2
2023-11-16 21:21:52    - Local:        http://d3e5e7d726ea:3000
2023-11-16 21:21:52    - Network:      http://172.17.0.2:3000
2023-11-16 21:21:52 
2023-11-16 21:21:52  ✓ Ready in 43ms
2023-11-16 21:21:48 npm WARN exec The following package was not found and will be installed: prisma@5.6.0
2023-11-16 21:21:52 npm notice 
2023-11-16 21:21:52 npm notice New minor version of npm available! 10.1.0 -> 10.2.4
2023-11-16 21:21:52 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.2.4>
2023-11-16 21:21:52 npm notice Run `npm install -g npm@10.2.4` to update!
2023-11-16 21:21:52 npm notice

yes

FROM node:20-alpine AS deps

#https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine
RUN apk update && apk add --no-cache libc6-compat && apk add git

WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci

# Rebuild the source code only when needed
FROM node:20-alpine AS builder
WORKDIR /app
COPY . .
COPY --from=deps /app/node_modules ./node_modules
ARG NODE_ENV=production
RUN echo ${NODE_ENV}
RUN npx prisma generate
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001

#copy next config js if not using default config
COPY --from=builder /app/next.config.js ./next.config.js
COPY --from=builder /app/public ./public
COPY --from=builder /app/package.json ./package.json

COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

COPY --chown=nextjs:nodejs prisma ./prisma/
COPY --chown=nextjs:nodejs bootstrap.sh ./

USER nextjs
EXPOSE 3000
ENV PORT 3000
CMD ["./bootstrap.sh"]

dockerfile here

Then in boostrap.sh

#!/bin/sh
# Run migrations
DATABASE_URL="file:./dev.db" npx prisma migrate deploy
# start app
DATABASE_URL="file:./dev.db" node server.js

nextConfig has output: 'standalone',

does the db have data in it?

Not atm. Although, not even console.log("hello") gets logged.

where are you checking the log?

Inside the docker container

so on the server side

for example, on the dev enviroment I am seeing this

hello
prisma:query SELECT `main`.`Todo`.`id`, `main`.`Todo`.`createdAt`, `main`.`Todo`.`updatedAt`, `main`.`Todo`.`title`, `main`.`Todo`.`content`, `main`.`Todo`.`done` FROM `main`.`Todo` WHERE 1=1 LIMIT ? OFFSET ?
[]

in docker, this doesn't get logged for some reason.

I've done some digging. If I create a function that runs onclick and console.log in there, it works.

Seems like it doesn't those when I load the page. Are there some exceptions for standalone mode?

import { prisma } from "@/db";
import Link from "next/link";
import { redirect } from "next/navigation";

async function createTodo(data: FormData) {
  "use server"

  console.log("TEST")

  const title = data.get("title")
  if(!title) {
    throw new Error("Title is required");
  }

  await prisma.todo.create({data: {title: title.toString(),content: 'Learn how to use Prisma',},})

  redirect("http://localhost:3000/")
}

export default function Home() {

  console.log("HELLO WORLD")

  return (
    <>
      <header className="flex justify-between items-center mb-4">
        <h1 className="text-4xl font-bold">Todos!!</h1>
      </header>
      <form action={createTodo} className="flex gap-2 flex-col">
        <input type="text" name="title" className="border border-slate-300 bg-transparent rounded px-2 py-1 outline-none focus-within:border-slate-100" />
        <div className="flex gap-1 justify-end">
          <Link href=".." className="border px-2 py-1 rounded">Cancel</Link>
          <button type="submit" className="border px-2 py-1 rounded">Create</button>
        </div>
      </form>
    </>
  );
}

so here, only TEST gets logged. HELLO WORLD never gets logged.

I don't get console.log in production build too

Hm, I see. Although, if I add an item in the DB I see the query:

prisma:query BEGIN
prisma:query INSERT INTO `main`.`Todo` (`id`, `createdAt`, `updatedAt`, `title`, `content`, `done`) VALUES (?,?,?,?,?,?) RETURNING `id` AS `id`
prisma:query SELECT `main`.`Todo`.`id`, `main`.`Todo`.`createdAt`, `main`.`Todo`.`updatedAt`, `main`.`Todo`.`title`, `main`.`Todo`.`content`, `main`.`Todo`.`done` FROM `main`.`Todo` WHERE `main`.`Todo`.`id` = ? LIMIT ? OFFSET ?       
prisma:query COMMIT

then it redirects it me back, and I don't see anything printed out - nothing on the screen as well.

If I extract the db, I can see the item I inserted inside.

I would expect to see the QUERY when I am redirected back. Makes sense if console logs arent there

do you see the item if you refresh the page

nope

try add export const dynamic = 'force-dynamic' in your page

and use revalidatePath("/") instead of redirect

revalidatePath didn't seem to work. Redirect worked fine

it works as expected though!

are there any advantages using revalidatePath here?

redirect cause the whole page refresh

not sure why revalidatePath didn't work tho. It just refreshed the page.

I am adding on /new, and listing on /

probably that's the reason?

so now redirect will update the data right?

just revalidatePath not updating?

well, will revalidatePath redirect for me?

because it's a different page

oh use redirect if it is not in the same page

i see

Why would I have to use this though?

export const dynamic = 'force-dynamic'

I thought they are in same file

because its static page by default

why did it work in the dev mode tho? If you don't mind explaining? 🙂

because the static page only being generated when you run next build

See, what seems strange to me is that I am redirecting back. Wouldn't that force the page to "reload"?

ahhh

Static rendering means that components are pre-rendered on the server at build time ( next build ). The result of this prerendering is cached and then served. Dynamic rendering means that components are rendered on the server at request time. The result of this (pre)rendering is not cached.

Well, to my understanding - every page with content that I want to update real-time or with user interaction (like tables, lists etc.) need to be dynamuic?

yes or use tag to revalidate after update

mhmm I see

and because I have
const todos = await prisma.todo.findMany()

this is not ran at build time, but at request

so build-time would be just hard-coded information, right? theoretically

it is run in build time if the page is static

And what'd you mean with this?

yes or use tag to revalidate after update

if you use fetch, it can be specific the cache strategy

Sorry for stupid questions, I'm coming from React/Node, so this is really new to me haha

welll, I shouldn't really need to use fetch right, if I get my data server side like now?

you can leave it dynamic or use cache and revalidate with tag after update

since you are using prisma, you cannot use the next fetch

that's why you need export const dynamic

or use unstable_noStore

Great, got it not! Thanks! 😄