[`Backend`]: refactor codebase for supporting more providers
moonlitgrace opened this issue · comments
Unfortunately mangareader seems down ( showing its for sale ).
Currently manga-api only relies on mangareader for data, but since it went down we gotta change provider.
Well I think its better if we can change whole codebase for supporting different providers, we need to scale ( currently this architecture isnt scalable ).
We will prolly change folder structure as well like
url can be like: /api/<provider>/<query>/
List of manga providers we can use: https://github.com/anshumanv/awesome-anime-sources#manga
Note: we might need to use selenium instead, well but its better if we can do this with selectolax itself.
P.S: mangareader isnt down, I entered wrong url :).
But we need to support multiple providers.
If anyone looking forward to contribute, please write here ❤️
Codebase refactoring is done. 🔥
Now need some more providers: we follow this pattern: provider_service_pattern
Also we take providers with SSR support, otherwise we need to use selenium to trigger javascript.
Way is slower than selectolax.
To check use curl like this:
curl <provider_site_url>If you can see full html then that site matches with our case, if the response contains something like:
Enable Javascript like context, then NO.