📱Using External Readers
Last updated
Last updated
If the built-in Web Reader is not enough for you, LANraragi's content can be consumed by multiple external applications who provide their own readers.
Dedicated LANraragi readers use the Client API to provide an experience closely matching the capabilities of the Web interface.
Here are some existing clients:
Features:
View and search your LANraragi database
View tags
Read archives
Bookmark archives to keep track of your current page
Sort archives by date (requires Timestamp tags to be enabled)
Features:
Archives list.
Search.
Archive overview and reader.
Bookmarks.
Multiple servers/profiles.
Manage your server from within the app.
Mihon, formerly Tachiyomi, and its forks use extensions that provide sources. The LANraragi extension is part of the Keiyoushi repository.
For automated updates add the repository by following these instructions. (recommended) For manual updates search for LANraragi on Keiyoushi's Extensions page.
There may be additional repositories not linked here that provide the extension but support is not guaranteed.
A React-based frontend PWA making use of the Client API. "Works best on mobile and tablet viewports, but the desktop experience is okay." Check it out here.
Some readers can leverage the OPDS Catalog exposed by LANraragi to visualize and read the available archives. Those programs can't exploit all of LRR's features(Search, Database backup), but they might have reading features you won't find in the current dedicated clients.
If your OPDS reader supports Page Streaming Extensions, LANraragi is compatible with it and will serve individual pages.
LRR supports OPDS PSE 1.1, which means that if you have server-side progress tracking enabled, you can pick up where you stopped reading from any OPDS client. Syndication!
The URL for the OPDS Catalog is [YOUR_LANRARAGI_URL]/api/opds.
You can use the Demo as an example.
Refer to your reader's documentation to figure out where to put this URL.
If you have No-Fun Mode enabled, remember that you'll need to add the API Key to this URL for the catalog to be available to your reader application.
You can either use the Bearer token approach like with regular API calls, or add ?key=[API_KEY] as a parameter to the URL.
The following readers have been tested with the OPDS Catalog:
The following readers haven't been tested but should work:
