From 98e27c8f251022320020716a9ef7a5b892ad2b61 Mon Sep 17 00:00:00 2001 From: Christophe Besson Date: Sat, 12 Sep 2026 13:48:09 +0200 Subject: feat(hub): the mail bounds are settings, with a panel to change them MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit They were constants in two modules, so an operator could not touch them without editing code and redeploying — and the hour a budget runs out is not when anyone wants to do that. `[mail]` in hub.toml carries the defaults; the live values live in `hub_settings`, read at each use. A missing row falls back to what the configuration file says, so an instance that never opens the panel behaves as its file describes. The panel sends only what changed, the hub clamps each value to a stated range and refuses a key it does not know, and the response is what gets rendered — so a clamped value is never shown as stored. `GET /v1/admin/mail` is the other half. There was no way to see any of this: a refusal was a line in the journal, so an instance that had stopped sending sign-up codes looked, from the panel, exactly like one with no sign-ups. It reports the hour's use, what is left for sign-ups, and what is left for recovery — the difference between those two being the reserved share made visible. Labels in all ten catalogues. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01T4YmK41VsEURWFdop4EEeT --- packages/meshbay-hub/src/meshbay_hub/app.py | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'packages/meshbay-hub/src/meshbay_hub/app.py') diff --git a/packages/meshbay-hub/src/meshbay_hub/app.py b/packages/meshbay-hub/src/meshbay_hub/app.py index 7b187df..82ae110 100644 --- a/packages/meshbay-hub/src/meshbay_hub/app.py +++ b/packages/meshbay-hub/src/meshbay_hub/app.py @@ -107,8 +107,14 @@ def create_app(cfg: HubConfig | None = None) -> FastAPI: await _backfill_email_hashes() + from meshbay_hub import hub_settings as _hub_settings from meshbay_hub import mail as _mail _mail.configure(cfg.identity.id) + # What `hub.toml` says the mail bounds are. The live values are read + # from `hub_settings` at each use, so an admin can change them from the + # panel while the hub is serving; these are what a missing row falls + # back to. + _hub_settings.set_mail_defaults(cfg.mail) if cfg.identity.admin_usernames: await _sync_admin_roles(cfg.identity.admin_usernames) -- cgit v1.2.3