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
It would be great if the following options could be available:
Download to requesting client directly. Could the downloaded data be redirected to the browser of the client and not download into the container/server at all? Not sure if this is possible without locally caching the file first? The use case I'm thinking of implementing another install for somebody else on their SBC that doesn't have much storage available.
As a secondary option, when downloading to the default location on the container/server - could the list of downloads made be presented to the client with an option to download them or delete them?
One workaround would be to present the downloads folder in Apache in the host - but a bit messy having two locations. Or maybe use rclone to sync changes to the client over scp etc.
The text was updated successfully, but these errors were encountered:
It would be great if the following options could be available:
Download to requesting client directly. Could the downloaded data be redirected to the browser of the client and not download into the container/server at all? Not sure if this is possible without locally caching the file first? The use case I'm thinking of implementing another install for somebody else on their SBC that doesn't have much storage available.
As a secondary option, when downloading to the default location on the container/server - could the list of downloads made be presented to the client with an option to download them or delete them?
One workaround would be to present the downloads folder in Apache in the host - but a bit messy having two locations. Or maybe use rclone to sync changes to the client over scp etc.
The text was updated successfully, but these errors were encountered: