Irrelevant “free” disk usage numbers

AI-generated summary

The discussion revolves around misleading free disk space numbers on the Discourse admin dashboard when uploads and backups are stored on S3. johnmuhl highlights that the displayed free space (e.g., 6.12 GB) doesn’t account for S3 storage, making it inaccurate. codinghorror clarifies this is not a bug but a feature, as the numbers reflect local disk usage. johnmuhl suggests a feature request to display free space available on the Discourse host separately from S3 backups. sam emphasizes the importance of showing host space, while johnmuhl agrees but argues the current placement next to S3-related metrics is misleading. Mittineague asks where the information should be displayed, and cpradio proposes a new column labeled “system” to show available space independently.

If you have uploads and/or backups set to go to S3 the free disk space numbers on the admin dashboard are misleading.

The 21.6 GB free is the amount of free space on the server hosting Discourse not on the S3 bucket hosting the uploads and backups.

Not a bug, that is how it is supposed to work.

I see what you mean. So this is a feature request to have the free space available on the host displayed elsewhere or at least not displayed when using S3 backed storage.

Space on host is critical I want that always displayed, if you reallly reallly really don’t want to show this, why not simply add a css rule?

I’m happy to have the space available on the Discourse host displayed somewhere. I just don’t think next to the uploads and backups numbers is the appropriate place when the uploads and backups are stored on a host with essentially unlimited space. It makes it look like Amazon only has 21.6 GB of free space.

2 curtidas

Where would you put it?
Mockup?

Maybe another column named “system”? with the space available listed next to it?

1 curtida