- Ya
- 9 Agosti 2026, 06:11 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 5b29e22
Almost everything an organization stores records its own size somewhere — an imgs row, a kb_media row, a mailbox measurement. Two things do not. Branding assets (logos, favicons, background images, theme CSS and config) are written straight into the public bucket under the organization's domain prefix, and the docs workspace is written under its id. Neither leaves anything in the database saying how large it is, so both read as zero. object_storage_days holds what a sweep reads back from the object store, bucketed by last-modified day so an arbitrary billing window sums exactly rather than rounding to whole months. **************** supplies size and last-modified, deduped by key across nodes. Site replication puts the same object on several nodes, and counting it once per node would multiply an organization's bill by the size of the cluster. BRANDING excludes the members/ subtree deliberately. Member avatars live under a fixed, organization-independent prefix by design — a user can belong to several organizations, so an avatar is not the property of any one of them — and the per-domain copies are legacy. Counting them would charge one organization for a file another organization's user owns. Schema verified in production before this landed: object_storage_days exists with its uniqueness constraint after a KI run.