doorae-server
Lightweight multi-agent chat server built with FastAPI, SQLite, and WebSocket.
Quick Start
pip install -e ".[dev]"
doorae-server init
doorae-server
Development
pip install -e ".[dev]"
pytest
Environment
All DOORAE_* variables are optional — the cluster auto-persists
runtime secrets in ~/.doorae/ on first boot. See .env.example
at the repo root for the full list. Highlights:
DOORAE_JWT_SECRET— session token signing key. Auto-generated at~/.doorae/jwt_secretif unset.DOORAE_MCP_SECRETS_KEY— Fernet key for encrypting MCP credentials (GitHub PATs, Linear keys, etc.) at rest in the DB. Auto-generated at~/.doorae/mcp_secrets_keyif unset so attached MCP instances survive restarts. Generate your own with:python3 -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())"
Losing this key invalidates all stored MCP credentials — they must be re-entered via the admin UI.DOORAE_DEV=1enables dev-mode conveniences (ephemeral MCP key fallback when persistence fails). Production must leave this unset so misconfigurations fail loudly at boot.
Metadata
Release files for drhub 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| drhub-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for drhub-0.7.0-py3-none-any.whl |
Release files / drhub-0.7.0-py3-none-any.whl
| Download URL | drhub-0.7.0-py3-none-any.whl |
|---|---|
| Size | 353.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fd817e745f16fad0f4e9a3470b96691a186d36f03ea2462bb1e15abbdc8a69e
|
|
BLAKE2b-256 checksum How to use checksums |
ff5d352042c61395414aac2902ced5f78e286fada3164ee8b96505568a83a922
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for drhub 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.