feat(web): storage cap frontend — sidebar indicator + admin Instance settings tab#102
Merged
Conversation
ravirajsinh45
added a commit
that referenced
this pull request
Jul 7, 2026
ravirajsinh45
force-pushed
the
feat/reap-stale-uploads
branch
from
d9f4484 to
9916b6b
Compare
ravirajsinh45
added a commit
that referenced
this pull request
Jul 7, 2026
ravirajsinh45
added a commit
that referenced
this pull request
Jul 7, 2026
… + Save disabled until loaded (review #102)
ravirajsinh45
force-pushed
the
feat/storage-cap-frontend
branch
from
50761e5 to
9b9a05a
Compare
ravirajsinh45
force-pushed
the
feat/reap-stale-uploads
branch
from
9916b6b to
b304e70
Compare
ravirajsinh45
added a commit
that referenced
this pull request
Jul 7, 2026
ravirajsinh45
added a commit
that referenced
this pull request
Jul 7, 2026
… + Save disabled until loaded (review #102)
ravirajsinh45
force-pushed
the
feat/storage-cap-frontend
branch
from
6f7db56 to
f516fe5
Compare
ravirajsinh45
force-pushed
the
feat/reap-stale-uploads
branch
from
b304e70 to
872907e
Compare
…ut + InstanceSettings type
settings/admin gains client-side Users | Instance settings sub-tabs; the Instance settings tab shows current used/limit and lets a superadmin set the cap in GB (0/blank = unlimited) via PUT /instance/settings + SWR mutate.
… + Save disabled until loaded (review #102)
…dicator into bottom section; remove redundant per-project indicator
ravirajsinh45
force-pushed
the
feat/storage-cap-frontend
branch
from
f516fe5 to
12b5966
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Frontend for the instance storage cap (backend #98). Stacked on #101 (top of the storage epic stack).
used / limit+ a meter (amber ≥80%, red ≥90%);usedonly when unlimited.settings/admingains client-side Users | Instance settings sub-tabs; the Instance settings tab shows current usage + a GB input to set the cap (0/blank = unlimited) →PUT /instance/settings+ SWRmutate(the sidebar refreshes live via the shared SWR key).<StorageUsage>component + purestorageMeterStatehelper +api.put+InstanceSettingstype. Branding untouched (clubbed into the tab group post-feat: Instance branding — white-label logos, org name, favicon, Powered by FreeFrame #90).Testing
tsc --noEmitclean; new vitest:storageMeterState/GB conversion (8),<StorageUsage>render limited+unlimited (2),InstanceSettingsTabsave→GB→PUT (2). All pass.api.test.tsstale fetch mocks;notification-store) predate this branch — proven by reverting to the parent. CI runs the web build, not vitest, so they've been silently red. Unrelated to this change; flagged for cleanup.Follow-ups