Skip to main content

BizOSaaS v2-Rebuild Implementation Plan

Source: Derived from docs/REBUILD_TASKS.md Status: ACTIVE

Overview​

This plan outlines the technical steps required to complete the BizOSaaS v2-rebuild, focusing on a lean architecture: "5 containers, 2 languages, 1 database engine."

Phase 0: Observability 🟢​

  • Deploy SigNoz to Dokploy.
  • Instrument Python and Next.js services with OTLP.
  • Create platform dashboards and critical alerts.

Phase 1: Foundation 🏗️​

  • Setup Turborepo monorepo with pnpm.
  • Shared packages: ui, db, config, types, api-client.
  • Single docker-compose.yml for core stack.
  • Migrate secrets to Infisical.
  • PostgreSQL consolidation (pgvector).

Phase 2: Unified Frontend 🌐​

  • Next.js 15 App Router initialization.
  • Multi-tenant middleware and Auth integration.
  • Port Dashboard, Admin, and Directory features.
  • Complete CRM and SEO Dashboard UI logic.
  • Finalize Payload CMS integration for tenant sites.

Phase 3: AI Service Consolidation 🤖​

  • FastAPI implementation for ai-service.
  • Port all agents (CrewAI) and connectors.
  • LLM Router and real-time cost tracking.
  • Webhook Bridge for low-code automation (Make/n8n).

Phase 4: BullMQ Workflows ⚡​

  • Replace Temporal with BullMQ for job processing.
  • Implement HITL (Human-in-the-loop) dashboard.
  • 29 standard workflows converted to BullMQ jobs.

Phase 5: Enterprise Auth & Social Login 🔐​

  • Configure better-auth Social Providers (Google, GitHub, LinkedIn, Microsoft).
  • Build premium OAuth UI buttons for Login/Register flows.
  • Implement automatic account linking and onboarding redirection.
  • Research SAML/OIDC support for Enterprise clients.

Phase 6: AI Architecture Refinement 🤖 (New)​

  • Consolidate 47 CrewAI agents by merging duplicate functionality into 20-Core Architecture agents.
  • Provide real capabilities for currently stubbed Analytics agents and Workflow crews.
  • Map Orchestrator patterns exclusively to the refined agent pool.

Current Mission: Phase 15 Coreldove Accelerator 🚀​

  • Google Drive inventory synchronization.
  • Multi-platform product scanning (Shopify, Amazon Ready, Flipkart Ready).
  • SEO promotion engine for product listings.
  • Viral Reels script generator based on stock levels.

Verification Protocol​

  1. Local Build: turbo run build must pass.
  2. Docker Check: docker compose build for all services.
  3. Deployment: CI/CD to Dokploy via GitHub Actions.

Phase 17: Production Deployment Blockers Fix 🔧 (March 2026) — ACTIVE​

Priority: CRITICAL — Must complete before VPS deployment.

17A — Fix Redis DNS (EAI_AGAIN bizosaas-redis)​

  • bizosaas-web is on both bizosaas-network + dokploy-network; redis is only on bizosaas-network
  • Fix: docker compose down && docker compose up -d (clean restart resets DNS)
  • If still fails: Add - dokploy-network to the redis: service's networks in docker-compose.yml

17B — Fix Health Check (Wrong Table Name)​

  • Health check queries "users" but the Drizzle table is named "user" (singular)
  • Fix: Change select count(*) from "users" → select count(*) from "user" in apps/web/src/app/api/health/route.ts
  • Also make the route return HTTP 200 even when DB query fails (graceful degradation)

17C — Add Payload Tables via Direct SQL​

  • drizzle-kit 0.31.7 crashes with a pg_constraint bug → Payload push: true never works
  • Fix: Add payload_migrations and payload_preferences as raw SQL entries in the startup.mjs TABLES array
  • Also: Delete the broken spawnSync Payload sync block from startup.mjs

17D — Push to GitHub & Deploy to VPS​

  • git add changed files → git commit → git push origin v2-rebuild
  • On VPS: git pull && docker compose build && docker compose up -d

dokploy curl command​

KVM8​

curl -X 'GET'
'https://dk8.bizoholic.com/api/project.all'
-H 'accept: application/json'
-H 'x-api-key: FCRmhXnyGnZARHJVNGMZOkPoFytPQjJlngLTwpqgPPlQTQKPGwxtpnzqxSbNbEMp'

KVM 2​

curl -X 'GET'
'https://dk.bizoholic.com/api/project.all'
-H 'accept: application/json'
-H 'x-api-key: nnsZhSTQXihvzCsZppVpEJllnNXiZoupWzHckPymYaKTmCCGtCzrAdstcdqBGfRn'

Phase 18: 🔧 March 18, 2026 — Build Unblock & Integration Fixes (COMPLETED)​

Priority: CRITICAL
Status: ✅ DONE — All fixes committed to v2-rebuild and pushed.

18A: Fix Next.js Build Error (Route Conflict) ✅​

  • Root Cause: apps/web/src/app/(payload)/admin/[[...segments]]/page.tsx conflicted with (admin)/admin/page.tsx. Both resolved to the same /admin URL segment. Next.js 15 enforces strict route specificity.
  • Fix: Deleted (payload)/admin/[[...segments]]/page.tsx. Payload CMS admin is correctly served at /cms via (payload)/cms/[[...segments]].
  • Updated: payload.config.ts admin meta configuration.
  • Commit: bb5f5230c — fix(web): remove duplicate /admin payload route causing Next.js build error
  • Build Result: Exit code 0 ✅ verified locally.

18B: Fix BizBot WebSocket 403 (CORS) ✅​

  • Root Cause: ai-service/ai-agents/main.py had allow_origins=["*"] with allow_credentials=True — Starlette rejects wildcard origins when credentials are enabled (HTTP 403).
  • Fix: Replaced allow_origins=["*"] with explicit list: app.bizoholic.com, api.bizoholic.com, admin.bizoholic.com, bizoholic.com, thrillring.com, localhost:3000.
  • Deployed via: git push origin v2-rebuild (awaiting Dokploy redeploy of ai-service).

18C: Multi-Channel Order Tracking Sync (Coreldove/T2.10) ✅​

  • Added tracking_id and courier fields to Order model in apps/ai-service/app/ports/ecommerce_port.py.
  • Updated list_multi_channel_orders in apps/ai-service/app/api/ecommerce.py to expose tracking fields.
  • Frontend E-Commerce Hub pages are already wired to display these fields.

18D: Internal Frontend Routing & Social Auth Fixes ✅​

  • Root Cause: apps/web/src/middleware.ts was not properly passing cleaned hostnames (without www) to the internal rewritten URL path, causing app/[domain]/page.tsx database tenant lookups to fail (e.g. searching for "www.thrillring.com" instead of "thrillring.com"). Also missing CORS config in better-auth.
  • Fix (Middleware): Strip www. before creating rewritten URLs and implemented a robust non-www to www redirect for root domains.
  • Fix (Auth): Replaced direct onClick values in social auth with async handlers catching errors and supplying callbackURL="/dashboard". Added extensive trustedOrigins in auth.ts to allow cross-subdomain logins.

18D: Next Steps (Pending Redeploy)​

  1. Trigger Dokploy redeploy of the core-stack compose app to pick up the route fix.
  2. Trigger Dokploy redeploy of ai-service (if separate) to pick up the CORS fix.
  3. Verify BizBot chat at app.bizoholic.com — WebSocket should no longer return 403.
  4. Run E2E onboarding test (Coreldove D2C scenario) once containers are healthy.
  5. Proceed with T2.5 (full onboarding flow test) and T2.16 (broken link audit).