How logan-larson/castify works
Main System Components
a) Client Layer:
• Mobile Applications (iOS/Android) built with Capacitor
• Web Application (SvelteKit)
• As separate but related frontend clients
b) API Layer:
• GraphQL API (shown by the /api directory with Apollo Server)
• Custom scalar definitions and resolvers
c) Database Layer:
• Neo4j Graph Database (evident from SQL files in /database)
• Main entities: Users, Podcasts, Episodes, and their relationships
d) Infrastructure Layer:
• Nginx reverse proxy
• Docker containers (shown by Dockerfiles and docker-compose.yml)
Component Relationships
a) Client-Server Communication:
• GraphQL queries/mutations flow between clients and API
• Main query types (podcasts.js and users.js resolvers)
b) Data Flow:
• Authentication flow (JWT tokens from utils/jwt.js)
• Podcast content delivery
• User interactions (follows, subscriptions, comments)
Detailed Component Breakdown
Frontend (app/):
• Components:
• Player components
• Authentication components
• Podcast/Episode components
• Stores management
Backend (api/):
• GraphQL schema and resolvers
• Database driver connection
• Authentication middleware
Key Features to Highlight
Specific flows for:
• Podcast playback system
• Social features (follows, comments)
• Authentication flow
• Content discovery
• Offline capabilities
Technical Stack Indicators
• SvelteKit
• GraphQL
• Neo4j
• Capacitor
• Docker
• Nginx
Deployment Architecture
Containerized structure:
• Docker containers relationship
• Nginx reverse proxy configuration
• Mobile build process
This architecture should reflect the project's current state while accommodating the roadmap items mentioned in the README, such as offline playback, enhanced player controls, and recommendation systems.