# umutkarakas34/fruittelegrambot architecture

> Architecture diagram of the GitHub repository umutkarakas34/fruittelegrambot, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-13). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/umutkarakas34/fruittelegrambot
- Repository: https://github.com/umutkarakas34/fruittelegrambot

## Overview

##### Project type and purpose
- Full-stack, play-to-earn web game with Telegram Bot integration.
- Frontend: React SPA (fruit-slicing game UI, pages, components).
- Backend: Node.js/Express API + Telegram Bot process + game logic + user/auth controllers.
- Persistent storage for users, games, tasks, referrals, daily check-ins, tokens, etc.

##### File structure for major components
- Frontend
– “frontend/fruit-slicing-game/src” contains React UI (App.js, pages, components, styles).
– “src/api/api.js” wraps HTTP calls to backend.
– Public assets in “public/” (HTML entry, images, audio).
- Backend
– “backend/app.js”: main Express app.
– “backend/bot.js”: Telegram Bot listener.
– “controllers/”: HTTP controllers for admin/user flows.
– “routes/”: routes wired to controllers.
– “middleware/”: authentication for users/admins.
– “models/”: MongoDB/Mongoose models (user, game, tasks, referrals, etc.).
– “utility/db.js”: DB connection.
– “upload.js”: file-upload handling.
– “.env” + “web.config” for deployment settings.

##### README for extra context
- Game logic and play-to-earn token conversion live in backend.
- Telegram Bot endpoints tie into same business layer.
- Frontend is standalone; backend still under active development.

##### Main components
- User Interfaces
– Web Browser (plays React game)
– Telegram Client (plays via Bot)
- Frontend SPA (React)
- Backend API (Express)
- Telegram Bot Process (bot.js)
- Database (MongoDB/other)
- External Services
– Telegram Bot API
– (Optional) Cloud storage/CDN for static files
– (Optional) Token/Crypto service if real tokens are minted

##### Relationships and data flows
- Browser → React SPA → HTTP(S) → Express API → DB
- Telegram Client → Telegram API → bot.js → Express controllers → DB
- Express may push notifications back via Telegram API for in-game events.
- Frontend polls or uses WebSockets (if implemented) to fetch game state.

##### Architectural patterns & design principles
- Three-tier architecture: Presentation (React), Application (Express + Bot), Data (MongoDB).
- MVC within backend: routes → controllers → models.
- Separation of concerns: auth middleware, file upload module, utility module.
- Environment-based config via .env.

##### Technology stack to annotate
- Frontend: React, Create-React-App, CSS modules.
- Backend: Node.js, Express, Mongoose (MongoDB ODM).
- Telegram Bot API (tdlib or node-telegram-bot-api).
- Authentication: JWT or session tokens (middleware).
- Deployment: IIS/Azure (“web.config”), PM2 (“ecosystem.config.js” in frontend), static host/CDN.

- All components clearly labeled.
- Brief notes on protocols, ports, or configs (e.g., port 3000 for Express).
- Critical paths: game play → scoring → token conversion → payout.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Clients Layer
    subgraph "Clients Layer"
        direction TB
        Browser["Web Browser"]:::client
        TelegramClient["Telegram Client"]:::client
    end

    %% Services Layer
    subgraph "Services Layer"
        direction TB

        subgraph "React SPA"
            direction TB
            APIClient["API Client"]:::service
            Pages["Pages"]:::service
            Components["Components"]:::service
            Styles["Styles"]:::service
            Utils["Utils"]:::service
            PM2Config["PM2 Config"]:::service
        end

        Bot["Telegram Bot Process"]:::service
        API["Express API"]:::service
    end

    %% Data & External Layer
    subgraph "Data & External"
        direction TB
        DB["MongoDB"]:::datastore
        TelegramAPI["Telegram Bot API"]:::external
        CDN["CDN/Static Host"]:::external
    end

    %% Interactions
    Browser -->|"loads SPA"| CDN
    Browser -->|"interacts"| APIClient
    APIClient -->|"HTTP REST"| API
    API -->|"Mongoose"| DB
    API -->|"Bot API calls"| TelegramAPI
    TelegramClient -->|"uses Bot"| TelegramAPI
    TelegramAPI -->|"Webhook"| Bot
    Bot -->|"internal API calls"| API
    API -->|"push notifications"| TelegramAPI
    APIClient -->|"poll/WebSocket"| API

    %% Click Events - Frontend
    click APIClient "https://github.com/umutkarakas34/fruittelegrambot/blob/main/frontend/fruit-slicing-game/src/api/api.js"
    click Pages "https://github.com/umutkarakas34/fruittelegrambot/tree/main/frontend/fruit-slicing-game/src/pages"
    click Components "https://github.com/umutkarakas34/fruittelegrambot/tree/main/frontend/fruit-slicing-game/src/components"
    click Styles "https://github.com/umutkarakas34/fruittelegrambot/tree/main/frontend/fruit-slicing-game/src/style"
    click Utils "https://github.com/umutkarakas34/fruittelegrambot/tree/main/frontend/fruit-slicing-game/src/utils"
    click PM2Config "https://github.com/umutkarakas34/fruittelegrambot/blob/main/frontend/fruit-slicing-game/ecosystem.config.js"
    click SPA "https://github.com/umutkarakas34/fruittelegrambot/tree/main/frontend/fruit-slicing-game/src"

    %% Click Events - Backend
    click API "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/app.js"
    click Bot "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/bot.js"
    click AdminCtrl "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/controllers/admin.js"
    click UserCtrl "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/controllers/user.js"
    click AdminRoute "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/routes/admin.js"
    click UserRoute "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/routes/user.js"
    click AuthAdmin "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/middleware/authenticateAdmin.js"
    click AuthUser "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/middleware/authenticateUser.js"
    click UM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/user.js"
    click GM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/game.js"
    click TM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/task.js"
    click DCM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/dailyCheckin.js"
    click RFM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/referral.js"
    click BM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/blog.js"
    click FM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/farming.js"
    click RLM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/relationships.js"
    click TIM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/taskImages.js"
    click UTM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/userTask.js"
    click ADM "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/models/admin.js"
    click DBUtil "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/utility/db.js"
    click Upload "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/upload.js"
    click Env "https://github.com/umutkarakas34/fruittelegrambot/blob/main/backend/.env"

    %% Styles
    classDef client fill:#cce5ff,stroke:#3399ff,stroke-width:2px
    classDef service fill:#d4edda,stroke:#28a745,stroke-width:2px
    classDef datastore fill:#fff3cd,stroke:#ffcd39,stroke-width:2px
    classDef external fill:#e2e3e5,stroke:#6c757d,stroke-width:2px
```
