AOS backend

Fresh-deployment Frappe v16 application for a globally deployed marketplace with account, commerce, media and communications domains.

Architecture

Frappe/MariaDB own canonical transactions and feature data. Redis/queues carry asynchronous work; a transactional outbox coordinates domain changes with Notifications, moderation, Analytics and external processing. Media owns durable object-storage references; companion HTTP services run on private infrastructure. Multiple web/workers must share database, cache, queue, secrets and object storage. No measured million-user capacity is implied.

The 26 current feature contracts have exactly one authoritative README each: feature index. Other global documentation: docs index, API reference, deployment, operations, backups and restore, load testing.

Fresh installation

Pinned runtime and dependency versions: CI versions and Python project metadata. Prepare the Frappe bench, private companion services and configuration from .env.example and the deployment runbook. Then install the app on a new site:

cd ~/frappe-bench
bench --site "$SITE" install-app aos
bench --site "$SITE" migrate
bench --site "$SITE" run-tests --app aos

Manual indexes are applied by schema-only post-model-sync installers and reasserted by aos.migrate.after_migrate. The canonical Reports reason master is installed through aos.install.after_install.

Static audit and deploy gates

Run from apps/aos:

python ci/validate_repository.py .
python ci/validate_api_documentation.py
python ci/validate_doc_paths.py
python ci/validate_fresh_backend.py

Do not deploy without server-side Frappe suite, private service tests, load/failover trials, signed callback tests and backup/restore verification.