# Ignore file for the @cloudpdf/server image build. # # The image is built with the repo root as the build context # (`docker build -f cloudpdf/server/Dockerfile .`). BuildKit honours the # `.dockerignore` that sits next to the Dockerfile, so this # file scopes the context for the server image without affecting any # other build. (A plain `cloudpdf/server/.dockerignore` would only apply when # the build context itself is `cloudpdf/server`, which it is not here.) # # Goal: keep the context small + deterministic. We deliberately keep all # workspace `package.json` files (turbo prune needs the full workspace # graph) and only drop build outputs, caches, VCS, and the giant native # submodules. # Dependencies + build outputs (regenerated inside the image) **/node_modules **/dist **/.turbo **/*.tsbuildinfo # Framework build outputs that also contain stray nested package.json # copies (these break `turbo prune` workspace discovery if included). **/.next **/.svelte-kit **/.vercel # VCS + tooling state .git **/.git .github .changeset .husky .claude .cursor .vscode .idea .DS_Store # Native source submodules (huge; not needed - we fetch a pinned # prebuilt libembedpdf and compile only the small N-API addon). packages/pdfium/pdfium-src packages/engine/runtime/runtime-src # pdf-runtime local build caches (regenerated by build:target). packages/engine/runtime/build/build packages/engine/runtime/build/cache packages/engine/runtime/build/generated packages/engine/runtime/build/libpdfium packages/engine/runtime/build/local-artifacts packages/engine/runtime/build/local-staging # Docs / site source (not needed to build the server; kept out of context # weight - their package.json still ships so the workspace graph resolves). website/.next website/out cloudpdf/website/.next cloudpdf/website/out # Test/coverage noise **/coverage **/.vitest