Chat Rage

1. Core Characteristics

• Application Name: ChatApi (v0.1.0)
• Release Name: dk168
• Project Type: Real-time Communication Platform
• Server Role: Backend API server with WebSocket support for live messaging
• Environment: Production-ready deployment

2. Folder Structure

Chat Rage/
├── bin/
│   └── dk168                          # Main Elixir Release Executable
├── erts-13.2.2.5/                     # Erlang Runtime System
│   └── bin/                           # BEAM VM & tools
│       ├── beam.smp (Parallel VM)
│       ├── erl, erlc (Compiler)
│       ├── epmd (Node Discovery)
│       ├── run_erl, to_erl (Console)
│       └── [13 executable tools]
├── lib/                               # Compiled Libraries & Dependencies
│   ├── chat_api-0.1.0/                # Main Application (Compiled)
│   │   └── ebin/
│   │       ├── Elixir.ChatApi.* (Core Modules)
│   │       ├── Elixir.ChatApiWeb.* (Web Controllers & Views)
│   │       └── [13 sample compiled beams]
│   ├── [55+ Dependency Libraries]
│   │   ├── appsignal_phoenix-2.0.7    # APM Monitoring
│   │   ├── phoenix                    # Web Framework
│   │   ├── postgrex-0.15.5            # PostgreSQL Driver
│   │   ├── redix-0.10.7               # Redis Client
│   │   ├── phoenix_pubsub_redis       # Pub/Sub Messaging
│   │   ├── joken-2.3.0                # JWT Tokens
│   │   ├── cowboy-2.8.0               # HTTP Server
│   │   ├── ex_aws_s3-2.0.2            # AWS S3 Storage
│   │   ├── ex_aws_ses-2.1.1           # AWS SES Email
│   │   ├── oban-2.1.0                 # Job Queue
│   │   ├── sentry-8.0.0               # Error Tracking
│   │   └── [40+ additional libraries]
│   └── elixir-1.17.3/ & runtime libraries
├── tmp/                               # Runtime Temporary Directory
│   ├── log/
│   │   └── erlang.log.1               # Erlang System Logs
│   └── pipe/                          # Named Pipes / IPC
├── .env.prod.livechat                 # Production Environment Config
├── createdb.sh                        # Database Initialization Script
├── migrate.sh                         # Database Migration Runner
├── seed.sh                            # Database Seeding Script
└── rollback.sh                        # Migration Rollback Script

3. System Architecture

┌─────────────────────────────────────────────────────────────────┐
│                        CLIENT LAYER                             │
│   (Web Browser / Mobile / Widget / Third-party Integration)     │
└────────────────────────────────────┬────────────────────────────┘
                                     │
                        ┌────────────┴────────────┐
                        │   HTTPS / WebSocket     │
                        └────────────┬────────────┘
                                     │
┌────────────────────────────────────▼──────────────────────────────┐
│                 ELIXIR / PHOENIX WEB SERVER                       │
│                      (dk168 Application)                          │
├───────────────────────────────────────────────────────────────────┤
│  • HTTP/WebSocket (Port 4012)  [Cowboy 2.8.0]                     │
│  • Request Routing & Controllers                                  │
│  • Session Management [Pow 1.0.20]                                │
│  • Authentication & Authorization                                 │
│  • Real-time Features (LiveView)                                  │
│  • Pub/Sub via Redis [phoenix_pubsub_redis 3.0.0]                 │
└────────┬─────────────────────┬──────────────────┬─────────────────┘
         │                     │                  │
    ┌────▼────┐          ┌─────▼──────┐    ┌─────▼──────┐
    │         │          │            │    │            │
┌───▼──┐   ┌──▼───┐   ┌──▼──────┐  ┌─▼────▼──┐ ┌──────▼─┐
│      │   │      │   │         │  │         │ │        │
│  DB  │   │Redis │   │ AWS S3  │  │ AWS SES │ │ Sentry │
│  PG  │   │PubSub│   │ Storage │  │ / Email │ │ / APM  │
│      │   │      │   │ Service │  │ Service │ │        │
└──────┘   └──────┘   └─────────┘  └─────────┘ └────────┘
   │
   └─ PostgreSQL Connection
      (DATABASE_URL: livechat_kanyaars_prod)

Key architecture components:

• Cowboy Server handles HTTP and WebSocket connections.
• Phoenix Framework provides MVC structure and real-time engine.
• Ecto / PostgreSQL provides persistence and query abstraction.
• Redis supports session storage, Pub/Sub, and caching.
• AWS Services handle file storage and email delivery.
• Oban executes background job processing.
• Joken / JWT enables token-based authentication.
• AppSignal provides APM and performance monitoring.

4. Tech Stack Summary

• Backend: Elixir 1.17.3 + Phoenix
• Database: PostgreSQL 12+ (Ecto ORM)
• Caching / Messaging: Redis
• Server: Cowboy (WebSocket support)
• Auth: JWT + Pow
• Storage: AWS S3
• Email: AWS SES + Customer.io
• Jobs: Oban
• Monitoring: Sentry + AppSignal
• Cloud: AWS ecosystem
• Integrations: GitHub, Slack, Expo

5. Tech Stack Detail

A. Core Runtime & VM

B. Web Framework & HTTP

C. Database & Persistence

D. Real-Time & Messaging

E. Authentication & Authorization

F. Cloud & External Services

G. Background Processing

H. Monitoring & Error Tracking

I. Data Formats & Parsing

J. Utilities & Helpers

K. Third-Party Integrations

L. Compilation & Tooling

M. Runtime Support Libraries

N. Infrastructure