How arrobalytics/django-ledger works
Project type and purpose
• Django Ledger is a full-stack Django application (a pluggable accounting engine) with both server-side components (models, forms, views, GraphQL API, management commands) and a client side UI (Webpack-built assets, templates, styles). It provides a high-level double-entry accounting API for Django projects and ships its own “dev_env” Django project for development/testing.
File structure
• Top-level directories:
• dev_env/ – a standalone Django project for local development (ASGI/WSGI, settings, urls)
• django_ledger/ – the accounting engine code:
– models/, forms/, views/, urls/, templates/, static/ – classic Django MVC layers
– io/ – file import core (OFX/QFX importer, middleware)
– contrib/django_ledger_graphene/ – GraphQL schema, mutations, API adapters
– management/commands – Django CLI extensions (e.g. generate_oauth2_codes)
• assets/ – front-end source (TypeScript, Less/SCSS), tsconfig, webpack.config.js, package.json
• docs/ & notebooks/ – user/developer documentation and examples
• Dockerfile & docker-compose.yml – containerization for development/CI
• README.md, Pipfile, setup.py, pyproject.toml – project metadata, dependencies, packaging
README for additional insights
• Confirms MVC pattern, GraphQL support, static-asset pipeline, Docker/dev environment, multi-tenant support, file import, financial reports.
Detailed checklist for the principal software engineer
• Dev_env Django project as a separate “development sandbox” connecting to the same core components
• To capture:
• HTTP server entry (ASGI/WSGI)
• URL routing (django_ledger/urls & dev_env/urls)
• Views & GraphQL resolvers
• Forms & validation
• Business modules (report, io, transaction engines)
• ORM & database
• Static file bundling & delivery
• External file import and management commands