feat(deploy): Optimize docker build time

[taiphanvan2k3]

Summary by CodeRabbit

• Chores
  • Optimized Docker build process with multi-stage builds and improved caching strategies.
  • Introduced a reusable base Docker image to reduce build times and image sizes.
  • Added Google Cloud Build configuration for automated container image generation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request introduces Docker build infrastructure for a .NET application with IronPDF support. It adds a Google Cloud Build configuration, Docker ignore patterns, a multi-stage Dockerfile using a prebuilt base image, and a new Dockerfile.base that installs system dependencies required by IronPDF.

Changes

Cohort / File(s)	Change Summary
Google Cloud Build Configuration build-base-dotnet.yaml	New Cloud Build configuration that builds and tags a Docker image using gcr.io/cloud-builders/docker, specifying the base Dockerfile and output registry path
Docker Ignore Patterns src/Web.Api/.dockerignore	New .dockerignore file with exclusion patterns for IDE files, build outputs, dependencies, sensitive files, and common repository artifacts
Multi-stage Dockerfile src/Web.Api/Dockerfile	Refactored to use multi-stage builds with a dedicated build stage (SDK 8.0), optimized COPY steps for layer caching, and final runtime stage using the prebuilt base image instead of direct ASP.NET runtime
Base Docker Image src/Web.Api/Dockerfile.base	New Dockerfile that constructs the base image with ASP.NET runtime 8.0, system dependencies via apt-get, manual libjpeg8 installation for IronPDF, font cache refresh, and directory setup

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• IronPDF system dependencies: Verify that all dependencies in Dockerfile.base are necessary and correctly specified, particularly the libjpeg8 manual installation and apt-get package selection
• Multi-stage build optimization: Review Dockerfile caching strategy and layer ordering to ensure build efficiency
• Docker ignore patterns: Confirm that exclusion rules in .dockerignore are appropriate and won't inadvertently exclude required artifacts
• Cloud Build configuration: Validate the registry path, image tagging, and Dockerfile reference are correct for the target environment

Poem

🐰 twitches nose at layered builds
Docker stacks so neat and clean,
IronPDF springs in between!
Base and runtime, cache refined—
Cloud-born containers, perfectly designed! ☁️✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Free

📥 Commits

Reviewing files that changed from the base of the PR and between ad73391 and fab8def.

📒 Files selected for processing (4)

• build-base-dotnet.yaml (1 hunks)
• src/Web.Api/.dockerignore (1 hunks)
• src/Web.Api/Dockerfile (2 hunks)
• src/Web.Api/Dockerfile.base (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}