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
I want to create an API based proxy for customizing reading lists based on tags and improving image quality.
Because I want to deploy on the same host, calling the download API will result in unnecessary file copying, especially if the files are too large.
It seems that there is file path information in the database. Can we add a file path field in the archive information API? This should solve most of the problems.
The text was updated successfully, but these errors were encountered:
I want to create an API based proxy for customizing reading lists based on tags and improving image quality.
Because I want to deploy on the same host, calling the download API will result in unnecessary file copying, especially if the files are too large.
It seems that there is file path information in the database. Can we add a file path field in the archive information API? This should solve most of the problems.
The text was updated successfully, but these errors were encountered: