# lollytim/full-stack-project-memories architecture

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

- Interactive diagram: https://gitdiagram.com/lollytim/full-stack-project-memories
- Repository: https://github.com/lollytim/full-stack-project-memories

## Overview

##### Project type and purpose
- This is a full-stack “memories” project with a React (or similar) client in the `client/` folder, and a Node/Express REST API server in the `server/` folder.
- Purpose: allow users to register/login and create, read, update, delete “memory” posts. Authentication is JWT-based.

##### File structure
- client/
- The front-end code (likely a React SPA).
- server/
- index.js – app bootstrap and mount point for routes and middleware.
- config/ – CORS and allowed origin configuration; reads from `.env`.
- routes/ – Express routers for `/posts` and `/users`.
- controllers/ – Request handlers implementing business logic per route.
- middleware/auth.js – JWT verification gate.
- models/ – Mongoose schemas: `user.js` and `postMessage.js`.
- .env – environment settings (e.g. DB URI, JWT secret).
- package.json / lock – dependencies (Express, Mongoose, CORS, etc.).

##### Architectural patterns & key technologies
- Layered (MVC-style) architecture:
- Routes → Controllers → Models → Database
- Middleware for cross-cutting concerns (auth, CORS).
- Tech stack:
- Front-end: React (client side routing, state management).
- Back-end: Node.js, Express.js, JWT auth.
- Database: MongoDB via Mongoose.
- Configuration: dotenv, CORS policy.

##### Main components
a. Client (React SPA)
– UI Components
– HTTP/API Service (axios or fetch layer)
b. API Server (Express)
– Router Layer (`routes/`)
– Controller Layer (`controllers/`)
– Middleware Layer (auth, CORS)
– Data Layer (Mongoose models)
c. Database
– MongoDB cluster or instance
d. External/Infrastructure
– Environment/config service (`.env`)
– Optional: Cloud storage or external auth if present

##### Relationships and data flow
- Client → (HTTP/JSON) → Express Router
- Router → Controller → (calls) → Model (Mongoose) → MongoDB
- Model → Controller → (HTTP/JSON) → Client
- Auth path: Client sends JWT in Authorization header → auth middleware validates → allows controller execution
- Config/CORS: Happens at server startup, applies to all incoming requests

##### Essential details to capture
- Environment/config (how the server reads DB URI and secrets)
- CORS policy (allowedOrigins.js, corsOption.js)
- auth.js middleware intercepting protected endpoints
- Two main resource flows: /users (registration, login) and /posts (CRUD)

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Client (React SPA)"
        SPA["React SPA"]:::frontend
        SPASvc["HTTP/API Service"]:::frontend
    end

    subgraph "Server (Express API)"
        env[".env"]:::config
        AO["allowedOrigins.js"]:::config
        CO["corsOption.js"]:::config
        pkg["package.json"]:::config

        subgraph Middleware
            auth["auth Middleware (JWT)"]:::middleware
        end

        subgraph Routes
            postsR["/posts Router"]:::layer
            usersR["/users Router"]:::layer
        end

        subgraph Controllers
            postsC["Posts Controller"]:::layer
            usersC["Users Controller"]:::layer
        end

        subgraph Models
            postM["PostMessage Model"]:::model
            userM["User Model"]:::model
        end
    end

    DB["MongoDB"]:::database

    %% Client to Server
    SPA --> SPASvc
    SPASvc -->|HTTP/JSON| postsR
    SPASvc -->|HTTP/JSON| usersR

    %% Config flow
    env --> AO
    env --> CO
    AO --> auth
    CO --> auth

    %% Auth path
    postsR --> auth --> postsC
    usersR --> auth --> usersC

    %% Controllers to Models
    postsC --> postM
    usersC --> userM

    %% Models to Database
    postM --> DB
    userM --> DB
    DB --> postM
    DB --> userM

    %% Response flow back to client
    postsC --> postsR --> SPASvc --> SPA
    usersC --> usersR --> SPASvc --> SPA

    %% Click Events
    click SPA "https://github.com/lollytim/full-stack-project-memories/tree/main/client/"
    click SPASvc "https://github.com/lollytim/full-stack-project-memories/tree/main/client/"
    click env "https://github.com/lollytim/full-stack-project-memories/blob/main/server/.env"
    click AO "https://github.com/lollytim/full-stack-project-memories/blob/main/server/config/allowedOrigins.js"
    click CO "https://github.com/lollytim/full-stack-project-memories/blob/main/server/config/corsOption.js"
    click auth "https://github.com/lollytim/full-stack-project-memories/blob/main/server/middleware/auth.js"
    click postsR "https://github.com/lollytim/full-stack-project-memories/blob/main/server/routes/posts.js"
    click usersR "https://github.com/lollytim/full-stack-project-memories/blob/main/server/routes/user.js"
    click postsC "https://github.com/lollytim/full-stack-project-memories/blob/main/server/controllers/posts.js"
    click usersC "https://github.com/lollytim/full-stack-project-memories/blob/main/server/controllers/users.js"
    click postM "https://github.com/lollytim/full-stack-project-memories/blob/main/server/models/postMessage.js"
    click userM "https://github.com/lollytim/full-stack-project-memories/blob/main/server/models/user.js"
    click pkg "https://github.com/lollytim/full-stack-project-memories/blob/main/server/package.json"
    click README "https://github.com/lollytim/full-stack-project-memories/blob/main/README.md"

    classDef frontend fill:#ADD8E6,stroke:#000,stroke-width:1px
    classDef config fill:#90EE90,stroke:#000,stroke-width:1px
    classDef middleware fill:#D3D3D3,stroke:#000,stroke-width:1px
    classDef layer fill:#98FB98,stroke:#000,stroke-width:1px
    classDef model fill:#E0FFE0,stroke:#000,stroke-width:1px
    classDef database fill:#FFA500,stroke:#000,stroke-width:1px,stroke-dasharray: 5 5
```
