Files
Aniworld/docs
Lukas f18c31a035 Implement async series data loading with background processing
- Add loading status fields to AnimeSeries model
- Create BackgroundLoaderService for async task processing
- Update POST /api/anime/add to return 202 Accepted immediately
- Add GET /api/anime/{key}/loading-status endpoint
- Integrate background loader with startup/shutdown lifecycle
- Create database migration script for loading status fields
- Add unit tests for BackgroundLoaderService (10 tests, all passing)
- Update AnimeSeriesService.create() to accept loading status fields

Architecture follows clean separation with no code duplication:
- BackgroundLoader orchestrates, doesn't reimplement
- Reuses existing AnimeService, NFOService, WebSocket patterns
- Database-backed status survives restarts
2026-01-19 07:14:55 +01:00
..
2026-01-16 20:30:25 +01:00
2025-12-15 14:07:04 +01:00
2026-01-18 11:56:22 +01:00
2026-01-16 20:30:25 +01:00
2025-12-15 14:07:04 +01:00
2025-12-15 14:07:04 +01:00

Aniworld Documentation

Overview

This directory contains all documentation for the Aniworld anime download manager project.

Documentation Structure

Document Purpose Target Audience
ARCHITECTURE.md System architecture and design decisions Architects, Senior Developers
API.md REST API reference and WebSocket documentation Frontend Developers, API Consumers
DEVELOPMENT.md Developer setup and contribution guide All Developers
DEPLOYMENT.md Deployment and operations guide DevOps, System Administrators
DATABASE.md Database schema and data models Backend Developers
TESTING.md Testing strategy and guidelines QA Engineers, Developers
SECURITY.md Security considerations and guidelines Security Engineers, All Developers
CONFIGURATION.md Configuration options reference Operators, Developers
CHANGELOG.md Version history and changes All Stakeholders
TROUBLESHOOTING.md Common issues and solutions Support, Operators
features.md Feature list and capabilities Product Owners, Users
instructions.md AI agent development instructions AI Agents, Developers

Documentation Standards

  • All documentation uses Markdown format
  • Keep documentation up-to-date with code changes
  • Include code examples where applicable
  • Use clear, concise language
  • Include diagrams for complex concepts (use Mermaid syntax)

Contributing to Documentation

When adding or updating documentation:

  1. Follow the established format in each document
  2. Update the README.md if adding new documents
  3. Ensure cross-references are valid
  4. Review for spelling and grammar