Skip to content

CavellTopDev/pitchey-app

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

664 Commits
Sorry, we had to truncate this directory to 1,000 files. 253 entries were omitted from the list.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Pitchey

A comprehensive movie pitch platform connecting creators, investors, and production companies through secure pitch sharing, NDA management, and real-time collaboration.

Quick Start

# Backend (Terminal 1) - MUST use port 8001
PORT=8001 deno run --allow-all working-server.ts

# Frontend (Terminal 2)
cd frontend && npm run dev

Visit http://localhost:5173

Documentation Index

Document Description
docs/ARCHITECTURE.md System architecture, design decisions, and infrastructure
docs/API_REFERENCE.md Complete API endpoints documentation (117+ endpoints)
docs/DEPLOYMENT.md Production deployment guide for Cloudflare Workers + Pages
CLAUDE.md Developer context and project-specific instructions

Production URLs

Tech Stack

  • Frontend: React + TypeScript + Vite + Tailwind CSS
  • Backend: Deno + Oak + Better Auth (session-based)
  • Database: Neon PostgreSQL with Hyperdrive pooling
  • Edge: Cloudflare Workers + Pages + R2 + Durable Objects
  • Cache: Upstash Redis (global distributed)
  • Real-time: WebSockets via Durable Objects

Demo Accounts

All accounts use password: Demo123

Portal Email
Creator alex.creator@demo.com
Investor sarah.investor@demo.com
Production stellar.production@demo.com

Mock Data Synchronization Workflow

When updating mock data, follow this workflow to ensure consistency:

  1. Update Frontend Mock Data (frontend/e2e/fixtures/test-data.ts)

    • Modify test fixtures with new mock data
    • Ensure IDs and relationships are consistent
  2. Update Backend Mock Responses

    • Update relevant service mocks in backend handlers
    • Ensure response structure matches frontend expectations
  3. Run Synchronization Check

    # Check for mock data inconsistencies
    npm run test:mock-sync
  4. Update E2E Tests

    • Update test assertions to match new mock data
    • Run E2E test suite: npm run test:e2e
  5. Document Changes

    • Update API documentation if response structure changed
    • Note breaking changes in CHANGELOG.md

For detailed testing procedures, see docs/TESTING_CHECKLIST.md

Support & Issues

License

Copyright © 2025 Pitchey. All rights reserved.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •