Files
Aniworld/docs
Lukas c4080e4e57 Fix Issue 9: Enforce configuration precedence rules
- Established explicit precedence: ENV vars > config.json > defaults
- Updated fastapi_app.py to only sync config.json when ENV var not set
- Added precedence logging to show which source is used
- Documented precedence rules with examples in CONFIGURATION.md

Key principle: ENV variables always take precedence, config.json is
fallback only. This ensures deployment flexibility and clear priority.

All config tests passing (26/26)
2026-01-24 21:23:48 +01:00
..
2025-12-15 14:07:04 +01:00
2026-01-23 15:25:47 +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