You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm using miniserve to exchange files with friends without going through some cloud service, it's very inconvenient that my best way to check if an upload is in progress is to mash F5 on the folder I'm sharing and check for changing file sizes, and my best way to check if a download is in progress is to fire up nethogs and check how much bandwidth miniserve is using.
It'd be very nice to have some kind of status indication in the terminal on the server side.
I can't currently make any promises about whether I'll get around to making a PR, given what a mess my other programming TODOs have been over the last few years, but the initial idea I have in case it inspires anyone else is basically:
One progress bar per in-progress transfer in the terminal
Progress bars color-coded to distinguish downloads from uploads
Transfers below a certain size or completing in less than a certain amount of time are either omitted or collapsed into a single "other activity " spinner/throbber to avoid a wall of progress bars when rendering an HTML file with its subresources.
When I'm using miniserve to exchange files with friends without going through some cloud service, it's very inconvenient that my best way to check if an upload is in progress is to mash F5 on the folder I'm sharing and check for changing file sizes, and my best way to check if a download is in progress is to fire up
nethogs
and check how much bandwidth miniserve is using.It'd be very nice to have some kind of status indication in the terminal on the server side.
I can't currently make any promises about whether I'll get around to making a PR, given what a mess my other programming TODOs have been over the last few years, but the initial idea I have in case it inspires anyone else is basically:
log
.The text was updated successfully, but these errors were encountered: