-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEAT: Storage API & Frontend #3409
FEAT: Storage API & Frontend #3409
Conversation
Oh wow, this is amazing! One suggestion would be to also display the total space, consumed space, and available space in human readable bytes. Or even in percentage as well. |
68c2b60
to
b9579e4
Compare
The storage is slow to calculate I assume due to dockerized file system. |
One thing is I need the depth to be full so that I can accumulate the camera directories sizes |
It might be better to run this command on stats initialization, include it in stats, and then just use that for the page. Maybe have it refresh every few minutes or something 🤔 |
Perhaps you can switch to
They have optimizations in speed over |
Thanks, ncdu appears to be faster and I think can work with the way I am using it |
32008eb
to
95d412d
Compare
95d412d
to
7c0a95c
Compare
With the new segment calculation in I am going to look in to a different frontend tool for displaying this info since it is clunky and I can't get good results |
8fde347
to
e459651
Compare
✅ Deploy Preview for frigate-docs canceled.
|
e459651
to
0a17177
Compare
I decided not to go with the graph / bar component. Seemed too random / difficult to work with and I think it is better that the styles match the new system page. |
I think it would be really cool to have a storage page in the frontend that displays the storage used by each camera so it is easier to visualize how that cameras retention settings contribute to overall storage use. Perhaps in a future PR management could be added but for now I think the information is helpful.
ToDo: