Production Deployment & CI/CD

This document outlines the deployment workflow and hosting configurations for Mockrithm. The production setup utilizes Vercel for hosting the application layers, Google Cloud Firebase for databases, and automated GitHub Actions for CI/CD pipelines.

1. Hosting Architecture Overview

Mockrithm runs as a multi-domain web service on Vercel:

• Root Domain (mockrithm.me): Serves marketing landing pages, pricing grids, and features.
• Documentation Subdomain (docs.mockrithm.me): Routes traffic to the Fumadocs collection handlers (/documentation/*).
• Dashboard Workspace: Managed dynamically on the root domain behind route guards.

graph LR
    DNS[Domain Name System] --> Router{Vercel Subdomain Router}
    Router -- host: mockrithm.me --> Landing[Marketing App Root]
    Router -- host: docs.mockrithm.me --> Docs[Fumadocs Route Handler]
    Router -- host: accounts.mockrithm.me --> Auth[Clerk Login/Signup Page]

2. Vercel Configuration Layout

To manage subdomain routing and redirect flows, Mockrithm includes a vercel.json deployment manifest:

{
  "version": 2,
  "cleanUrls": true,
  "rewrites": [
    {
      "source": "/documentation/:path*",
      "destination": "/app/documentation/:path*"
    }
  ],
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        {
          "key": "X-Frame-Options",
          "value": "DENY"
        },
        {
          "key": "X-Content-Type-Options",
          "value": "nosniff"
        },
        {
          "key": "Referrer-Policy",
          "value": "strict-origin-when-cross-origin"
        }
      ]
    }
  ]
}

3. Step-by-Step Vercel Deployment

Deploy the application by completing these setup stages:

npm install -g firebase-tools
firebase login
firebase deploy --only firestore:indexes

4. Webhook Integrations Setup

To keep external systems in sync, configure these webhooks: