How rizqyn9/rdev-web works
Main Application Components
a) Client-Side Layer
• Browser environment where the client-side JavaScript runs
• Entry.client.tsx as the main client entry point
• Routing system (routes directory structure)
b) Server-Side Layer
• Entry.server.tsx as the main server entry point
• Server/index.ts as the production server
• Server/dev-server.js for development environment
Key Architectural Components
a) Frontend Components (app/components/)
• UI Components
• Pages Components
• Typography Components
• Hooks
b) Core Services (app/services/)
• Blog Service
• Database Service (db.server.ts)
• Redis Service (redis.server.ts)
• Storage Service
• Email Service (resend.server.ts)
c) Routing Layer (app/routes/)
• Main Routes
• Action Routes
• SEO Routes
• Blog Routes
External Services Integration
Connections to external services:
• Cloudinary (utils/cloudinary.server.ts)
• ImageKit (utils/imagekit.server.ts)
• Redis
• Database (likely PostgreSQL/MySQL based on the schema files)
Data Flow Representation
• Client-Server communication
• API calls to external services
• Data flow between services
• Server-side rendering flow
Specific Implementation Details
Specialized components:
• MDX compilation system (compile-mdx.server.ts)
• SEO handling (seo.ts, root-seo.ts)
• Asset handling (public directory)
• Authentication flow (if present)
Deployment Architecture
Deployment flow:
• Docker container (Dockerfile)
• GitHub Actions workflow
• Fly.io deployment (fly.toml)
Drawing Instructions: