How bulatenkom/manga-updater works
Project type and purpose
• This is a full‑stack web application consisting of:
• A Python‑based asynchronous REST API server (“manga‑updater” backend) that scrapes external manga sites, maintains application state, schedules tasks, and provides data over HTTP.
• A Vue3 & Quasar SPA client that consumes the API to display manga lists, detail pages, and chapter content.
File structure
• Top‑level directories:
• backend/ – REST server code, parsers, models, async event loop, persistence, requirements.
• frontend/ – Web UI built with Vue3, Quasar, Vite, organized into components, pages, router, store, assets.
• doc/ – documentation and screenshots.
• Key backend modules:
• main.py – entrypoint for FastAPI/uvicorn.
• async.py, parsers.py – event‑loop orchestration and site‑specific scraping logic.
• db.py – persistence layer (disk‑backed state).
• models.py, msgspec_hooks.py – data schemas and serialization hooks.
• utils.py, exceptions.py – shared helpers.
• Frontend structure follows typical SPA pattern:
• src/router – route definitions.
• src/store – global state management.
• src/pages & src/components – views and reusable UI.
• Quasar config, assets, env declarations, CSS.
README for additional insights
• Backend uses FastAPI, uvicorn, asyncio, BeautifulSoup4, msgspec, structlog, rich.
• Core features: scraper tasks, state save/load (manga_list, monitoring_list, download_deque, task_queue), next‑chapter estimation.
• Client uses Vue-router, Quasar CLI/Vite.
• Development uses a CORS proxy for local testing, separate “dev.sh” to launch server on port 8000 and proxy on 7777.
Essential architectural elements
• Event‑loop and task‑queue are visible, because the core of this app is asynchronous scraping and scheduling.
• Boundary between front‑end and back‑end.