ASI Database Node API

Production URL: https://asi-database-node-api.arybit.co.ke

FastAPI diagnostics, a live interactive operator console, dual-engine database tooling, and Azure deployment scripts for asi-database-node-api.

The backend is in backend/, static UI in ui/, SQL in Database/, and Azure tooling in deploy-database-api/.

Read the documentation index, database connection guide, deployment guide, and SQL catalog. Generated HTML starts at ui/doc/index.html, served after deployment at production documentation.

Local development

python -m venv .venv
source .venv/bin/activate
python -m pip install -r backend/requirements.lock -r backend/requirements-dev.txt
python tools/verify.py
python -m pytest backend/tests -q -p no:cacheprovider
cd backend
python -m uvicorn app:app --host 127.0.0.1 --port 8080

The local API provides /health, /healthz, /ready, /version, and interactive /docs. Production disables interactive OpenAPI documentation. A successful readiness probe checks SELECT 1, not schema correctness. The live operator console opens at / and /admin/ after deployment. Public health checks update automatically; database and service operations require the private VM operator token. See console operations.

Production configuration

The production:13 target example uses asi-database-node-api.arybit.co.ke. The VM version is independent of the public hostname. Review existing private deployment.targets.json separately; set the canonical domain, DNS and certificate aliases before deployment. Runtime allowed hosts and CORS derive from the selected target. The public UI follows its current HTTPS origin.

bash init-deploy-database-api.sh
bash run.sh --13 --staging --plan
bash run.sh --13 --staging --preflight

Production is the default environment. Automatic deploy/core can authenticate with Azure, publish source to main and wait for exact-commit CI. Review deployment before running cloud operations. Cleanup can remove disks and data.

Database status

PostgreSQL and MySQL connectivity probes are supported. The PostgreSQL 16+ tenant/ledger foundation is experimental; it does not implement all legacy products. The legacy MySQL migration stream is disabled pending qualification. Schema changes, tenant isolation, backup restoration and public HTTPS require separate acceptance. Use SSH-tunneled database connections and private credentials; the production HTTPS URL is not a database socket.

Generate HTML documentation

python -m pip install -r tools/requirements-docs.txt
python tools/build-docs.py
python tools/build-docs.py --check

Every Markdown guide in docs/ is rendered under ui/doc/, alongside README and a reference for every SQL file. See documentation maintenance. SQL licensing is preserved in Database/LICENSE (repository file).