-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What we added
Integrated 60db.ai as a TTS provider alongside ElevenLabs. TTS_PROVIDER env var picks the primary; the chain falls through
automatically. 60db gets the same treatment as ElevenLabs: disk cache, 10-min circuit breaker, and usage/cost tracking (shown in
/status and /stats). Off by default, so existing behavior is unchanged.
How to use it
In .env:
SIXTYDB_API_KEY=sk_live_your_key
TTS_PROVIDER=sixtydb # or 'elevenlabs' (default) / 'openai'
Then docker compose up -d. Send /status on Signal to confirm TTS provider: sixtydb + 60db: ✅ active.
Chain: sixtydb → 60db → ElevenLabs → OpenAI → Polly (each falls back if a provider fails).