Administrator & deployment guide Work in progress
Work in progress (WIP)
This section contains technical documentation for system administrators, DevOps engineers, and developers hosting or contributing to the LITEfile application.
LITEfile is built as a lightweight, production-grade Django ASGI web application designed for high security, low operational overhead, and straightforward deployment on modern container platforms like Fly.io, AWS ECS, or Kubernetes.
Technical stack at a glance
- Backend runtime: Python 3.12 with Astral uv package manager
- Web framework: Django 5.2 (ASGI) with Gunicorn and Uvicorn workers
- Database: SQLite (local development) / PostgreSQL with connection pooling (staging & production)
- Static assets: WhiteNoise with compression and cache manifests
- Document storage: AWS S3 with pre-signed URLs and IAM least-privilege policies
- E-filing integration: Tyler Technologies EFM / EFSP REST API
- AI / OCR engine: OpenAI-compatible LLM gateway with MarkItDown PDF processing
Guides in this section
- System architecture: Core components, data flow, and request lifecycle.
- Configuration & environment variables: Complete reference of all required and optional environment variables.
- Deployment guide: Step-by-step instructions for deploying to Fly.io, configuring AWS S3, and managing database migrations.
- Local development & testing: Setting up your local development environment, running Pytest, executing Playwright end-to-end filing tests, and linting.
Operations and support handover
- Filing-code operations: daily freshness/worker checks, resync versus rebuild/backfill, reader grants and capacity prerequisites.
- Staff onboarding: separate support and analyst paths, scoped roles, TOTP/recovery and policy gates.
- Service maintenance index: existing handoff, preparation/security references with ownership and evidence requirements.
- Documentation and screenshot review: current evidence, publication checks and partner handover exercise.
- Shared maintenance register: content, technical and approval owners, enabled state, evidence and review triggers.
Internal developer notes stay in the repository and are linked where needed; these public entry points do not publish their contents as Docusaurus pages.