Directus CMS (Retired)
Status: RETIRED (Phase 5b completed, May 2026)
Directus has been fully replaced by the built-in CRM. All buyer portal data sources now read from Drizzle/Postgres directly. The 13 Directus-related setup scripts are archived under
scripts/archive/.This page is kept for historical reference only.
What Replaced It
Section titled “What Replaced It”| Legacy (Directus) | Replacement |
|---|---|
| CRM | Built-in CRM (/admin/* pages internally; browser URLs use clean paths) |
| Data API | Drizzle ORM queries on same Postgres |
| File uploads | R2 with presigned URLs |
| OpenImmo import | CPX22 worker box (Phase 8) |
| Per-client containers | Single multi-tenant deployment |
History
Section titled “History”Directus 11 served as the admin/CMS backend during the main branch era. Each client had their own Directus Docker container on the shared VPS, managed through Dokploy. The schema collections (units, agents, pages, portal_settings, unit_images) were mirrored as Drizzle tables when the spike/cf-runtime architecture was built.
The data from Directus was migrated to Postgres in Phase 5b via scripts/seed-local-data.mjs, which reads from the static JSON fallback files that had been the data source.