Prevent Payload from requiring DB access during Docker build

[static hatch]

Hey everyone! 👋
I’m deploying a Payload CMS instance using Docker (with one Node container and one Postgres container). For the build process, I’m using a GitLab CI pipeline.

Since I don’t want to expose my Postgres database to the outside world, I’m running into issues during the Docker build - Payload tries to connect to the database (e.g. for page generation).

Is there a recommended way to handle this?
Can I disable page/static generation during the build phase or somehow defer DB-related operations until runtime? My goal is to keep the DB closed off, especially during CI/CD builds.

Any tips or best practices would be much appreciated 🙏

[versed trail]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Migrations - Running migrations in production
• What is Payload?
• Production Deployment - Docker

Community-Help:

• Admin Route Serverless Function Timed Out ( In production only )
• PayloadCMS Upload field: how does it work?
• Application crashing in docker
• Custom Select Component (for field type relationship)