Demoing a NextJS project

anjanesh

I have scaffolded a default NextJS 16.1.1 project (TailWindCSS 4.1 + shadcdn 3.6.2 + TypeScript 5.5.4) with some input screens to be shown as a demo - (intended to be wired to a Django API for writing purpose later on).

npm run dev is working as expected so far - now I want to upload this to my server - I ran npm run build - now which folders of /myNextJSProject/.next/ should I upload to /home/myUsername/apps/opalstack/myNextJSProject so that it'll be available at https://myUsername.opalstacked.com/myNextJSProject ?

ls in my .next folder shows this :

app-path-routes-manifest.json
build
BUILD_ID
build-manifest.json
cache
dev
diagnostics
export-marker.json
fallback-build-manifest.json
images-manifest.json
next-minimal-server.js.nft.json
next-server.js.nft.json
package.json
prerender-manifest.json
required-server-files.js
required-server-files.json
routes-manifest.json
server
static
trace
trace-build
turbopack
types

next export has been removed in favor of 'output: export' in next.config.js.

sean

anjanesh typically you'd take the contents of the build directory and upload that into a static app, then serve that static app from whatever URL.

If the build directory is already on the server then you could skip the upload step and use a static symlink app pointing to the build directory.

anjanesh

Thanks - yes - build command writes to an out folder which I uploaded to my opalstack folder and it got served properly as a static-only site.

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  /* config options here */
    basePath: '/myNextJSProject',
    output: "export",
};

export default nextConfig;

What I want my NextJS project to be served in a non-static way ? Like how I run npm run dev locally ? Then do I need to create it as a nodeJS application in OpalStack and have it served as npm run start ?

"scripts": {
  "start": "next start -p $PORT"
}

nick

anjanesh We offer a NextJS installer in the dashboard that you can use as a base. Just replace the default project by building your own. The start/stop scripts are already provided, and cron to keep the process active.