Compare commits

3 Commits

Author SHA1 Message Date
9e45d51ed2 Mark sitemap route as force-static
Its content (fixed routes + blog post list) never needs per-request
dynamic execution, so pin it explicitly rather than relying on Next's
default inference.
2026-07-13 20:23:53 +05:30
ce602a454f Revert to standalone output: static export cannot run the SMTP Server Action
output: "export" produces pure static HTML with no server at runtime, so
the contact form's Server Action (src/actions/sendEmail.ts, nodemailer/SMTP)
can never execute under it - Next.js itself refuses to build with a Server
Action present under output: "export". The deploy architecture is being
switched to a Node standalone runtime (see doormile-build) instead, which
supports the existing Server Action unchanged.
2026-07-13 20:18:59 +05:30
0ec150d703 Revert to static export output for nginx deploy pipeline
output: "standalone" (a8f4b23) produces a Node server bundle with no
server.js at the path the deploy Dockerfile expects. The deploy repo's
Dockerfile now runs nginx serving static files (d808317), which requires
a static export (out/), not a standalone server bundle.
2026-07-13 20:09:35 +05:30

View File

@@ -1,6 +1,8 @@
import { MetadataRoute } from "next";
import { blogPosts, SITE_URL } from "@/data/blog";
export const dynamic = "force-static";
export default function sitemap(): MetadataRoute.Sitemap {
const staticRoutes = [
"",