OTO
deployment · from ARCHITECTURE.md at v0.6.1

Environment variables

None are needed for ordinary use.

Variable What it does
OTO_DB Serve a database from an explicit path instead of the project layout. oto query sets it.
OTO_PROJECT_CONFIG Point the engine at a project config, so a database alone is enough to query.
<SLUG>_DB The per-project form of OTO_DB, for an installed server.
OTO_STORE sqlite or neo4j: which store the engine serves, over the project's serve.backend. oto serve --backend sets it.
NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD (or NEO4J_AUTH=user/password) Where the Neo4j load goes and what serves from it. The uri may also live in the project config; the credentials never do.
OTO_DENY_TERMS Terms the publishability gate refuses. See GATES.md.
OTO_ONTOLOGIES, OTO_PACKS, OTO_REGISTRIES Where user and fetched ontologies and packs live, and the registries file.
OTO_REGISTRY_TOKEN, OTO_QUERY_REPO_TOKEN, OTO_ENGINE_TOKEN Tokens for private ontology registries, the query repository, and the engine repository in workflows.
OTO_SERVE_TOKEN The bearer token oto serve --http requires from every caller when it is set, and demands before binding beyond localhost.
PYTHON Which interpreter tools/run_gates.sh uses.