Skip to content

TECHNICAL.md

Latest commit

 

History

History
98 lines (74 loc) · 3.49 KB

TECHNICAL.md

File metadata and controls

98 lines (74 loc) · 3.49 KB

Technical Specifications

🏠 Home | 🇷🇺 Russian Version

Important

Architectural Paradigm: This project emphasizes extreme decoupling, built-in type-safety via Astro Content Collections, and stateless integrations. This completely removes the need for a database or backend administration panel, dramatically shrinking the attack surface while maintaining full interactivity and content dynamism.

🧩 Architectural Topology

The data flow is strictly unilateral, securing environment variables and executing sensitive operations purely on the server side.

graph TD
    A["Client Browser"] -->|HTTP/HTTPS| B["Nginx / Reverse Proxy"]
    B --> C["Docker Container (Astro App)"]
    
    subgraph "Server-Side Infrastructure"
      C -->|Pre-rendered Pages| D["Astro SSG Engine"]
      C -->|Dynamic API Routes| E["Astro Bun SSR"]
      E -->|Data Validation| F["Zod Schema Validator"]
      F -->|Sanitization| G["HTML Sanitizer"]
    end
    
    G -->|Secure POST Request| H["Telegram API"]
    
    subgraph "Content Management"
      D -.-> I["Astro Content Collections (Markdown/MDX)"]
    end
Loading

🔐 Security Architecture

  1. XSS Protection: All user inputs in forms are automatically sanitized via server-side logic (sanitize-html) running on the Astro Bun backend to prevent script injection.
  2. Environment Masking: Internal keys (BOT_TOKEN, CHAT_ID) are rigorously masked. The client is completely unaware of these values.
  3. Container Isolation: The multi-stage Dockerfile utilizes Bun Alpine, enforcing a root-less execution protocol at runtime for operational security.

🚀 CLI Commands

To replicate this environment locally, follow the standards below:

# Package manager standard
bun install

# Start development server
bun run dev

# Build for production
bun run build

# Run TypeScript/Astro type checks
bun run check

🚢 CI/CD Deployment Flow

sequenceDiagram
    participant Dev as "Developer"
    participant GH as "GitHub (main)"
    participant Coolify as "Coolify CI/CD"
    participant Server as "Production Server"

    Dev->>GH: push commit
    GH->>Coolify: Webhook trigger
    Coolify->>Server: Pull code & build Docker image
    Server-->>Coolify: Build successful
    Coolify->>Server: Deploy new container (Zero-Downtime)
Loading

Alexios Odos  |  Aliaksei Patskevich
Software Engineer • Code, Design & AI
GitHub • Telegram