How levish0/mofumofu works
Project Type and Purpose
• Mofumofu is a full-stack social blogging platform built with a microservices architecture.
• It includes:
• A web frontend (SvelteKit)
• A desktop app (Tauri + Svelte)
• A set of independent backend services (Rust, Python, Bun)
• Background processing via Celery
• Data and storage components (PostgreSQL, Redis, Meilisearch, Cloudflare R2)
High-Level File Structure
• Top-level directories:
• mofumofu-ui/ → Web UI (SvelteKit, TypeScript, TailwindCSS)
• mofumofu-desktop/ → Desktop app (Tauri + Svelte)
• mofumofu-backend/ → Core backend services and microservices
– src/ → Main API (Rust + Axum + SeaORM)
– tasks/ → Task API and Celery tasks (Python + FastAPI + Celery)
– markdown-service/→ Markdown rendering service (Bun + Elysia)
– migration/ → DB migration scripts (SeaORM)
• assets/ → Branding and image files
• CI/CD, Docker and deployment descriptors in .github/ and at project root.
Key Architecture Insights from README
• Architecture follows microservices split into layers:
Frontend Layer → API Gateway → Core Backend Services → Background Processing → Data & Storage
• Each service runs on its own port and can scale independently.
• API Gateway (Caddy or Cloudflare) routes traffic to public services.