Royal Glow internal docs · now fully interactive — Steps, API tables, file trees & live status
Royal Glow Docs

Project Status

Live snapshot of build progress and production-readiness — what's done, what's in flight, and the path to launch.

Project Status

A candid, current snapshot of where the platform stands. Use this before planning a release or onboarding someone new.

Not launch-ready from the current working tree yet. The codebase is feature-complete through Phase 10, but an in-flight refactor must land and be verified before promotion to production. Details below.

Build at a glance

Codebase

Feature-complete through Phase 10 — all 38 tables, both apps, CMS, docs, jobs, CI.

Branch

Active development on `dev`. Promotion flow: dev → test → pprd → prod.

Blocker

web → admin background-job relocation is mid-refactor and uncommitted.

Payments

Phase 1 = cash / UPI / card at the counter. No online gateway by design.

What's built

Data & domain

All 38 tables across 13 domains in packages/db — schema, relations, and a full typed query layer.

Customer app (apps/web)

Homepage, services, the 4-step booking dialog, bookings, profile, membership, gems, offers, blog, gallery, legal pages, auth/onboarding, PWA, SEO, and consent.

Admin app (apps/admin)

Dashboard, bookings, billing, customers, leads, staff, schedule, leave, memberships, offers, services, branches, users, reports, logs, integrations — plus the full admin API surface.

Platform

CMS (apps/cms), this docs site, the invoicing service, 19 background jobs, CI + deploy workflows, and a large unit/property test suite.

What blocks production right now

These are sequenced — finish them in order before promoting to prod.

Before you can launch (ops checklist)

None of this is code-blocked — every integration no-ops without a key. This is provisioning + verification. See the full Launch Runbook and Deployment.

AreaAction
SecretsAll keys in GitHub + Cloudflare env (canonical names in Environment Variables)
DNStheroyalglow.in, www, admin, status, docs + SSL
OAuthGoogle consent-screen approval (can take days — start early)
DataSeed the Neon prod branch; create the first Owner
CI gateslint · typecheck · unit · E2E · Lighthouse (a11y = 100) · k6 · security
MonitoringBetterStack monitors + job heartbeats live, or crons fail silently
Backupsweekly-backup.yml wired to R2 buckets + secrets

Path to launch

Land the refactor

Commit the web → admin job relocation; confirm both apps typecheck and build green (closes task 4).

Clear schema drift

bun run generate + drizzle-kit check; commit any new migration.

Provision

Keys, DNS, email-domain verification, Google OAuth approval; seed prod.

Pass the gates & promote

Green CI at the T-24h gate, then promote dev → test → pprd → prod following the Launch Runbook.

OpenReport an issue

Was this page helpful?

On this page