Greptile Overview

Summary

Fixed Docker build failure caused by missing NEXT_PUBLIC_APP_URL environment variable during the build stage. The build process requires this variable because next.config.ts accesses env.NEXT_PUBLIC_APP_URL, which triggers validation through @t3-oss/env-nextjs.

The fix follows the existing pattern established for DATABASE_URL by providing a dummy value during build time that runtime environments can override with actual values.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix follows the exact same pattern already established for DATABASE_URL in the same Dockerfile. It provides a dummy environment variable during build time that will be overridden at runtime. The approach is consistent, well-commented, and solves a critical build failure without introducing any new risks.
• No files require special attention

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant Docker as Docker Build
    participant Dockerfile as app.Dockerfile
    participant NextJS as Next.js Build
    participant EnvSchema as env.ts (t3-oss)
    participant NextConfig as next.config.ts
    
    Docker->>Dockerfile: Start build stage
    Dockerfile->>Dockerfile: Set DATABASE_URL dummy
    Dockerfile->>Dockerfile: Set NEXT_PUBLIC_APP_URL dummy
    Dockerfile->>NextJS: Run `bun run build`
    NextJS->>NextConfig: Load next.config.ts
    NextConfig->>EnvSchema: Import env (triggers validation)
    EnvSchema->>EnvSchema: Validate NEXT_PUBLIC_APP_URL (required)
    Note over EnvSchema: With fix: validates successfully<br/>Without fix: throws error
    EnvSchema-->>NextConfig: Return validated env
    NextConfig->>NextConfig: Access env.NEXT_PUBLIC_APP_URL (lines 85-93, 115)
    NextConfig-->>NextJS: Return config
    NextJS->>NextJS: Complete build
    NextJS-->>Docker: Build artifacts ready

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}