danvics/openreader
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
openreader/docs-site/docs/integrations/custom-openai.md
Richard R 9b9206f50d refactor(audiobooks): migrate audiobook pipeline to object storage 
This commit restructures the audiobook generation and serving layer to rely exclusively on S3-compatible blob storage, removing the dependency on local filesystem paths.

- Bundle `ffmpeg` and `ffprobe` binaries via npm to ensure portability across environments.
- Update API routes to stream audio directly from blob storage instead of local disk.
- Remove legacy migration endpoints and filesystem-based indexing logic.
- Add startup scripts to facilitate the transition from local to remote storage.

BREAKING CHANGE: Audiobook functionality is now strictly dependent on S3 configuration. The previous filesystem-based storage method has been removed.
2026-02-11 02:44:34 -07:00

827 B
Raw Blame History

title
Custom OpenAI

Use any custom OpenAI-compatible TTS service with OpenReader.

Use this integration when your endpoint is not directly covered by built-in dropdown defaults.

Compatibility requirements

Your provider should expose:

  • GET /v1/audio/voices
  • POST /v1/audio/speech

OpenReader setup

  1. In OpenReader settings, choose provider Custom OpenAI-Like.
  2. Pick model Kokoro, Orpheus, or Other as appropriate.
  3. Set API_BASE to your service base URL.
  4. Set API_KEY if required by your service.
  5. Choose voice.

Notes

  • API_BASE is required for this provider path because OpenReader cannot infer your custom host.
  • If voices do not load, verify the /v1/audio/voices response format.
  • For variable details, see Environment Variables.