Building a project without a database connection

[wesdimiceli]

I'm in the process of taking our existing production v2 implementation and working through the migration guide for v3. One issue that I can't seem to resolve is getting a NextJS production build without needing to set the secret or Mongo connection details in the config. Right now I'm basically looking at a stock v3 template and trying to run pnpm build gives me:

> cross-env NODE_OPTIONS=--no-deprecation NODE_ENV=production next build

  ▲ Next.js 15.0.0-canary.173
  - Experiments (use with caution):
    · turbo

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
   Collecting page data  ...Error: Error: missing secret key. A secret key is needed to secure Payload.

...

> Build error occurred
Error: Failed to collect page data for /admin/[[...segments]]

Even if I set a dummy secret, it will still fail on attempt to connect to Mongo, depending on what connection string is set in the local environment files. Previously, we had the disableDBConnect option but it doesn't seem to be supported by the v3 config.

Feels to me like universal best practice is to avoid production secrets in the repo and/or sitting around in developers' .env files, but the example READMEs suggest something along the lines of "copy the .env.example file and fill in the blanks". Which is fine for dev tasks but in order to get a usable docker image I need an environment-agnostic build that I can push to ECR, and putting secrets or database credentials in that image would be a pretty big security violation.

I'm not clear on what the database connection is used for during the build process, but I can imagine there could be a lot of instances where a DB connection is not practical -- e.g. DB lives in a private subnet, or some CI/CD configurations where a local database isn't feasible. Is there any way to achieve what I'm looking to do here? It would be great if there were some official documentation surrounding best practices w.r.t. using an encrypted secrets store like AWS SecretsManager or SSM. As it stands, the current Dockerfile examples don't seem to cover how to handle production secrets.

[andershermansen]

I do not think payload itself and the admin panel requires the db connection.

But if you put any pages which uses payload to fetch data (like probably the templates does). Then it will need to contact payload to build those pages.

Try to remove those pages and see if it will build without then.

[wesdimiceli]

Thanks. I don't think this is the case in my situation. The admin's root layout initializes Payload which always tries to establish a DB connection. When the connection fails, the build errors out. That means some DB needs to be available even if it's not used in the build process.

[rob-at-airwalk]

did this get resolved? we have the same issue

[wesdimiceli]

For me, I tracked it down to a component in the import map that was initializing payload. I'd check there to see if anything might be calling into payload in your codebase. Personally, I find these aspects of nextjs to be unintuitive so I guess it takes a little trial-and-error.

[spaaacetoast]

I also ran into this issue, specifically I was calling a server action from a server side component. what I didn't forsee was that it would call on the global instance of payload during the prerendering... Causing the build to fail :(

Thanks to you all I figured it out :)