soroush.asadi
8488acb115
Build backend images / build content-svc (push) Failing after 31s
Build backend images / build file-svc (push) Failing after 30s
Build backend images / build gateway (push) Failing after 30s
Build backend images / build identity-svc (push) Failing after 30s
Build backend images / build notification-svc (push) Failing after 31s
Build backend images / build render-svc (push) Failing after 31s
Build backend images / build studio-svc (push) Failing after 31s
Per-scene preview thumbnails for templates. Admin clicks "ساخت پیشنمایش صحنهها" → one single-frame AE render per scene → content.scenes.snapshot_url → shown as a thumbnail in the admin scene list (and available to the studio). - migration 30_render_snapshot_jobs.sql: render.snapshot_jobs (queued|running| done|error, per scene, image_url). - render-svc: db/snapshotjobs.go (EnqueueSceneSnapshots, List, Claim, SetResult -> writes content.scenes.snapshot_url cross-schema, SetError); handlers/ snapshotjobs.go (admin POST/GET /v1/scene-snapshots/:project_id + node-facing internal claim/result/fail); main.go routes; gateway route. - devworker: RunSnapshots — fulfils snapshot jobs with a generated placeholder PNG (data: URL, scene-key-tinted) so the flow is verifiable without an AE node. Gated by RENDER_DEV_SNAPSHOTS (default off; never hijacks real render jobs). - admin UI: ProjectScenes "generate snapshots" button (enqueue + poll + reload) and a thumbnail (snapshot_url || image) per scene row. Verified e2e via the dev mock: enqueue -> jobs run -> content.scenes.snapshot_url populated -> scenes API returns it -> admin renders the thumbnail. Remaining (C2): node-agent real-AE runner — claim snapshot, aerender -s0 -e0 -> ffmpeg still -> upload to a PERMANENT URL (mirror file-svc, not the time-limited export presign) -> post result. Needs a live AE node to build + verify. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
FlatRender
AI-powered video and image creation platform. Create professional videos and images with templates, a drag-and-drop studio, and one-click export.
Products
- Video Maker — timeline editor, Konva canvas, scene browser, transitions, audio, nexrender export
- Image Editor — Konva canvas, filters, crop, background removal, layer system
- Video Trimmer — ffmpeg.wasm in-browser trim + crop + export
- Templates — browsable marketplace with category sidebar
Quick Start
npm install
cp .env.example .env.local # fill in your credentials
npm run dev # http://localhost:3000
Related Repos
| Repo | Path | Purpose |
|---|---|---|
| flatrender | D:\Projects\flatrender |
This repo — Next.js app |
| flatrender-admin | D:\Projects\flatrender-admin\admin-api |
.NET 10 Admin API |
| flatrender-admin | D:\Projects\flatrender-admin\admin-ui |
React Admin SPA |
Stack
- Next.js 15 App Router · TypeScript · Tailwind CSS · shadcn/ui
- Supabase — auth, database, storage
- Stripe — subscription payments
- React-Konva — canvas editor (video + image)
- next-intl — Persian (default) + English i18n
- ffmpeg.wasm — browser-side video trimming
- nexrender — server-side After Effects rendering
Environment Variables
See .env.example for the full list. Minimum required to run:
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
Without Supabase the app runs in mock mode (studio uses localStorage).
Database Migrations
Run in order in Supabase SQL Editor:
supabase/migrations/001_profiles.sqlsupabase/migrations/002_render_jobs.sqlsupabase/migrations/003_projects.sql
Admin Panel
The admin panel at D:\Projects\flatrender-admin manages templates, categories, and media. When ADMIN_API_URL=http://localhost:5000 is set, the Next.js app fetches live data from it. Without it, hardcoded fallback data is used.
See CLAUDE.md for full development guide.