A Next.js app in a container needs one setting most tutorials skip: output: "standalone" , which trims the build down to only the files next start actually needs instead of the full node_modules tree. Get that right and the rest of a Next.js deploy on Ownkube is a normal git push.
This walks through deploying a Next.js app (App Router or Pages Router, both work) on Ownkube Compute: the standalone build, environment variables split between build time and runtime, an optional managed Postgres for apps using an ORM, and automatic TLS.
TL;DR
Set output: "standalone" in next.config.js so the Docker image ships a minimal server instead of the whole node_modules folder.
Push the app with a Dockerfile , and Ownkube builds it, deploys it, and issues TLS automatically on your *.ownkube.app hostname.
NEXT_PUBLIC_* variables get baked into the build; everything else is a runtime environment variable set in the dashboard.
Add an Ownkube-managed Postgres database if you use Prisma or another ORM, and point the…