soroush.asadi
3fc7bf2b97
Build backend images / build content-svc (push) Failing after 3m39s
Build backend images / build file-svc (push) Failing after 52s
Build backend images / build gateway (push) Failing after 58s
Build backend images / build identity-svc (push) Failing after 1m21s
Build backend images / build notification-svc (push) Failing after 1m0s
Build backend images / build render-svc (push) Failing after 58s
Build backend images / build studio-svc (push) Failing after 55s
AI SEO content generator - content-svc: per-tenant OpenAI config (ai_settings) + /v1/ai endpoints (settings GET/PUT, seo-post) with SEO-expert prompt → structured article - admin UI to configure token/base-url/model and generate + save as blog - configurable base URL for restricted networks Full data-driven admin panel - generic /api/admin/resource proxy + reusable AdminResource component - categories/tags/fonts/blogs (CRUD), users (list + ban), plans/slides - AI content section; nav + i18n i18n localization sweep - localized 116 user-facing + studio/editor components to next-intl (fa+en) under the auto.* namespace; merge tooling in scripts/merge-i18n.js Branding + assets - Monoline F logo (LogoMark + favicon) - offline SVG placeholder generator (/api/placeholder), dropped picsum.photos Fixes - JWT issuer mismatch on content/studio (flatrender → flatrender-identity) - missing role claim → [Authorize(Roles="Admin")] now works (RBAC) - Secure cookies broke HTTP sessions → gated behind AUTH_COOKIE_SECURE - Radix RTL via DirectionProvider (right-aligned menus in fa) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
FlatRender V2 — Database Schemas
PostgreSQL 15+. Single database, one schema per microservice.
Run order
Apply migrations in numerical order:
psql -d flatrender -f migrations/00_setup.sql
psql -d flatrender -f migrations/01_identity_tenants.sql
psql -d flatrender -f migrations/02_identity_users.sql
psql -d flatrender -f migrations/03_identity_billing.sql
psql -d flatrender -f migrations/04_identity_gamification.sql
psql -d flatrender -f migrations/05_content_taxonomy.sql
psql -d flatrender -f migrations/06_content_projects.sql
psql -d flatrender -f migrations/07_content_scenes.sql
psql -d flatrender -f migrations/08_content_characters_presets.sql
psql -d flatrender -f migrations/09_content_cms.sql
psql -d flatrender -f migrations/10_studio_saved_projects.sql
psql -d flatrender -f migrations/11_render_nodes.sql
psql -d flatrender -f migrations/12_render_jobs.sql
psql -d flatrender -f migrations/13_file_manager.sql
psql -d flatrender -f migrations/14_notification.sql
Schemas
| Schema | Owner Service | Purpose |
|---|---|---|
identity |
Identity Service (.NET) | tenants, users, auth, plans, payments, gamification |
content |
Content Service (.NET) | templates, scenes, presets, blogs, CMS |
studio |
Studio Service (.NET) | user's saved projects + audio (music/voiceover/sfx) |
render |
Render Orchestrator (Go) | jobs, nodes, frame jobs, snapshots, exports |
file_mgr |
File Service (Go) | user files, folders, quotas, cleanup |
notification |
Notification Service (Go) | in-app, push, email, SMS, telegram |
Cross-schema design
Schemas are loosely coupled. Where it matters for integrity (within a service), FKs are used. Across services, FKs are deliberately omitted so services can evolve independently — referential integrity is enforced via service code and events.
Hard FKs across schemas (intentional)
identity.earned_gifts.notification_id→notification.notifications.id
Everything else uses soft references (column documented but no FK).
Multi-tenancy
identity.tenants is the root of multi-tenancy. The default FlatRender
tenant has UUID 00000000-0000-0000-0000-000000000001.
Every user, project, render job, file, and notification carries a
tenant_id. Resellers (B2B API customers) are tenants. White-label
branding, API keys, webhooks, and usage metering all hang off
identity.tenants.*.
New features (vs V1)
- Multi-tenancy / Reseller API:
identity.tenants,tenant_branding,tenant_api_keys,tenant_webhooks,tenant_usage_daily - Voiceover support:
studio.saved_projects.voiceover_*,render.render_jobs.has_voiceover - Per-track volume:
music_volume,sfx_volume,voiceover_volume - Scene snapshots:
render.snapshotswith cache key - AE crash tracking:
render.node_crashes+ auto-recovery - Frame repair jobs:
render.frame_repair_jobs - AEP local cache on nodes:
render.node_template_cache(LRU) - SVG color previews:
content.template_svg_previews(drop image → traced SVG) - PWA push subscriptions:
identity.push_subscriptions - MFA:
identity.mfa_factors - Multipart uploads:
file_mgr.upload_sessions - Cleanup scheduler:
file_mgr.cleanup_schedules - Per-user / per-channel notification preferences:
notification.notification_preferences
Partitioning
Time-series tables are partitioned monthly (initial partition for 2026-01 created; ops creates new ones via cron):
identity.tenant_api_request_logsrender.node_health_logs
Service user grants
Each microservice connects with its own DB role limited to its schema.
See top of 00_setup.sql for the recipe.