feat(pipeline): per-project AE templates, and a workspace that fits any show
Deploy / deploy (push) Successful in 7m4s

Initialise Workspace built UNG_101..UNG_117 from a hardcoded range and
imported one hardcoded AEP, and fourteen findComp calls named UNG's comps
literally. None of it worked for a second show.

Comp names now follow a convention derived from the show id —
{showId}_VFX_OVERLAY, {showId}_EXPORT_TEMPLATE, _SHOW LUT — which
reproduces UNG's existing names exactly, so nothing changes for the show
it was written for. A project whose template departs from the pattern can
override any of the three.

Paths cannot be derived: UNG's show id is UNG while its folder is
UNGO_VFX. Those live on Project.pipelineConfig and are edited under
Project → Settings → Pipeline. They are resolved server-side and handed
to the panel with the project list, and read by buildPreviewManifest for
the headless build, so the panel and the farm cannot disagree about which
template — or which show LUT — a shot was built with. That mattered more
than the folder names: a preview rendered through another show's LUT is
quietly the wrong colour rather than obviously broken.

Episode folders come from the project's episode list, falling back to the
folders under its footage root for a show whose episodes are not entered
yet.

Panel 2.5.0. Adds migration 20260814010000_project_pipeline_config.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
twotalesanimation
2026-08-15 08:24:40 +02:00
parent 483db65eb3
commit bada122f42
12 changed files with 430 additions and 45 deletions
@@ -58,6 +58,13 @@ interface ProjectTabsClientProps {
startDate: Date | null;
slackWebhook: string | null;
slackChannel: string | null;
pipelineConfig: {
templateAep?: string | null;
rendersRoot?: string | null;
overlayComp?: string | null;
previewComp?: string | null;
lutComp?: string | null;
} | null;
};
clients: Client[];
teamMembers: TeamMember[];
+7
View File
@@ -201,6 +201,13 @@ export default async function ProjectPage({ params }: { params: Promise<{ id: st
startDate: project.startDate,
slackWebhook: project.slackWebhook,
slackChannel: project.slackChannel,
pipelineConfig: project.pipelineConfig as {
templateAep?: string | null;
rendersRoot?: string | null;
overlayComp?: string | null;
previewComp?: string | null;
lutComp?: string | null;
} | null,
}}
clients={clients}
teamMembers={teamMembers}
+13 -1
View File
@@ -1,5 +1,6 @@
import { NextRequest, NextResponse } from "next/server";
import { db } from "@/lib/db";
import { resolveProjectTemplates } from "@/lib/render-pipeline/project-templates";
// ── Auth ─────────────────────────────────────────────────────────────────────
@@ -50,11 +51,22 @@ export async function GET(req: NextRequest) {
status: true,
startDate: true,
dueDate: true,
pipelineConfig: true,
_count: {
select: { shots: true },
},
},
});
return NextResponse.json({ projects, total: projects.length });
// Templates are resolved here rather than in the panel so that the panel and
// the headless preview build cannot disagree about which template, or which
// show LUT, a shot was built with.
const withTemplates = await Promise.all(
projects.map(async ({ pipelineConfig, ...project }) => ({
...project,
templates: await resolveProjectTemplates({ ...project, pipelineConfig }),
}))
);
return NextResponse.json({ projects: withTemplates, total: withTemplates.length });
}