Skip to content

Storage: Manage storage in Cloud Vault and a "Where space goes" size map - #2061

Closed
joepio wants to merge 7 commits into
developfrom
claude/project-thread-xezgvb
Closed

joepio wants to merge 7 commits into
developfrom
claude/project-thread-xezgvb

Conversation

@joepio

@joepio joepio commented Oct 5, 2026 •

Copy link
Copy Markdown
Member

Requested by Joep · project thread

Before: the Cloud Vault card only said "40% used", and nothing showed which items take the space.

After, two parts:

  1. Cloud Vault card: "Manage storage" shows a breakdown by kind (change history, snapshots, files and images, search index), how much can be freed safely ("Free up space"), and the part kept only for undoing deletions (separate "Free it anyway" button with a warning).
  2. A "Where space goes" page (/app/storage, linked from the server card on the sync page): a WizTree-style size map of the workspace. One tile per item, area proportional to size, files and edit history in different colours, click a folder to look inside, plus a sorted list underneath for phones.

How: new GET /drive-usage/breakdown returns every resource in a drive with its Loro (history) and blob (file) bytes, with the same accounting as /drive-usage (shared files counted once). The page builds the folder tree from parent, rolls sizes up and lays tiles out with a squarified treemap (helpers/storageMap.ts, unit tested). The Cloud Vault part needs the GET /api/cloud-vault/{drive}/usage and POST .../free-up endpoints from the paired atomic-saas PR on the same branch name; the size map works on any server.

Screenshots (components rendered in isolation with sample data) are in the project files under storage-manage/. Server test drive_usage_endpoint now also checks that the breakdown adds up to the drive totals. Not yet run against a live drive.

Shows what the vault's storage is made of and how much can be freed, keeping
the part held only for undo separate and behind its own explicit button.
@joepio joepio self-assigned this Oct 5, 2026
GET /drive-usage/breakdown returns every resource in a drive with its edit
history and file bytes. The app draws them as a squarified treemap with
drill-down and a sorted list, reachable from the sync page.
@joepio joepio changed the title Cloud Vault: Manage storage panel with a breakdown and Free up space Storage: Manage storage in Cloud Vault and a "Where space goes" size map Oct 5, 2026
@joepio
joepio marked this pull request as ready for review October 5, 2026 09:46
joepio added a commit that referenced this pull request Oct 6, 2026
One tested commit for the open PRs of 5 October: link device to account (#1948), one profile form (#1953), faster branch runs (#1956), end-to-end encrypted conversations (#1971), passkey ceremony header (#1972), Flutter account package (#2035), cheap canvas undo (#2053), atomic.place tab title (#2056), table resource cell (#2057), small table fixes (#2058), storage map (#2061), Sync page cloud ladder (#2072), several served-domain suffixes (#2073), one sign-in (#2074), smaller chat messages (#2077), bring-along e2e fix (#2078), inline row data loss (#2079), Retry-After (#2080), #2070, #2071, #2066, #2067, #2068, #1969, #1887, #1897 and #1920.

Compressed stored values from #2077 stay readable, but a downgrade cannot read compressed rows.

Co-authored-by: Joep Meindertsma <joep@ontola.io>
@joepio joepio closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant