$ show vastsa/FileCodeBox
FileCodeBox is a file and text sharing service built with FastAPI and Tortoise ORM. It allows users to upload files or text accessible via short codes, with features including time/count-based expiration, chunked uploads, pre-signed URLs for direct cloud storage uploads, and an admin dashboard for management. The architecture uses a modular design with separate apps for base functionality and admin, storage abstraction for multiple backends (local, S3, OneDrive, WebDAV, OpenDAL), and background tasks for cleanup. Key entry points include main.py (FastAPI setup), apps/base/views.py (public sharing endpoints), and apps/admin/views.py (admin interfaces). The service demonstrates solid engineering practices with reusable components like storage abstraction and security headers, though some areas like settings management and rate limiting show opportunities for improvement in distributed environments.
The LLM identified 5 files worth highlighting for reuse:
Defines a clear interface for storage backends (FileStorageInterface) with implementations for local, S3, OneDrive, WebDAV, and OpenDAL. Enables switching storage mechanisms without application changes by returning framework-agnostic StoredDownload/StoredFile objects. Demonstrates excellent separation of concerns and is easily extractable for other projects needing pluggable storage.
Contains the build_attachment_headers function that generates HTTP headers to force file downloads (Content-Disposition: attachment) and prevent MIME sniffing/XSS attacks. This small but critical security component is used uniformly across all file-serving endpoints, is framework-independent, and addresses a common vulnerability in file-sharing services.
Manages application settings with layered defaults (hardcoded, database, environment variables), caching with TTL, and forced reload on updates. Uses the KeyValue model for persistent storage and provides a clean dependency injection pattern. This reusable pattern solves runtime configuration updates without service restarts and is isolated from web framework specifics.
Implements IPRateLimit class for in-memory, IP-based rate limiting used across endpoints (upload, login, etc.). While designed for single-instance deployments, the implementation is clean, testable, and demonstrates thoughtful abuse prevention. Could be adapted to use shared caches like Redis for horizontal scaling.
Handles chunked upload endpoints that receive file chunks, store them temporarily, and assemble final files on completion. Includes concurrency safety via upload IDs and integrates with background cleanup for incomplete uploads. This robust implementation of a complex feature is isolated from storage specifics (uses local temp storage) and showcases careful edge-case handling.