How arora200/medialib works
Project type and purpose
• This is a full-stack Python “medialib” server built on Flask (app.py, api.py).
• It exposes an HTTP/REST API and a user-facing web UI (Jinja2 templates under /templates and static files under /static).
• It manages media assets (documents, images, videos, links), stores metadata in a relational database (instance/media.db or another RDBMS via SQLAlchemy + Alembic), and persists media files on disk.
File structure
Top-level directories and files reveal the main layers:
• /templates & /static → frontend presentation (HTML, CSS, JS)
• app.py, api.py → request routing: web routes and REST endpoints
• forms.py, utils.py, models.py → business logic and data models
• /migrations + alembic.ini → DB schema versioning (SQLAlchemy + Alembic)
• instance/media.db, schema.sql → local DB file or schema definitions
• media_service.py, backup_script.py → background services (media ingestion, backup)
• pixabay_downloader.py, video_downloader.py → external-API workers to fetch media
• tests/ → test suite (pytest)
• docs/ → Sphinx documentation
• setup.sh, linux_setup.sh, run.bat → deployment & startup scripts
README.md
• Plain description: “media server with api – Manage Doc, Images, Videos, Links…”