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.
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.