`blackbull.config`¶

`blackbull.config` ¶

Declarative application configuration — :class:AppConfig.

AppConfig is a small, typed, immutable holder for the server-facing settings that :meth:blackbull.BlackBull.run (and :func:blackbull.serve) already accept as keyword arguments. It lets an application declare those settings once::

from blackbull import BlackBull, AppConfig

app = BlackBull(config=AppConfig(
    port=8443,
    certfile='cert.pem',
    keyfile='key.pem',
    workers=4,
))

if __name__ == '__main__':
    app.run()          # picks up the config; no flags to thread through

Resolution precedence in :meth:BlackBull.run is, highest to lowest:

an explicit keyword argument to run(...) — app.run(port=9000) always wins;
the value declared on the bound :class:AppConfig (if any);
the built-in default baked into :func:blackbull.serve.

AppConfig deliberately mirrors only the parameters serve already exposes — it is not a general-purpose settings store. Per-request and server-tuning knobs (window sizes, timeouts, queue depths beyond the two listed here, …) continue to live in :mod:blackbull.env and are sourced from BB_* environment variables.

host is intentionally absent: BlackBull's socket layer binds dual-stack on all interfaces (see :meth:blackbull.server.ASGIServer.open_socket), so a per-interface host field would silently do nothing. Use unix_path or inherited_fd for non-TCP binds.

`AppConfig` `dataclass` ¶

Immutable, declarative startup configuration for a BlackBull app.

Every field corresponds one-to-one with a keyword argument of :func:blackbull.serve / :meth:blackbull.BlackBull.run. Fields left at their sentinel default (None, or 0 for port, or False for reload) defer to serve's own built-in default unless an explicit run(...) argument overrides them.

blackbull.config¶