Skip to content

docs(deepgram): note that the Engine port must stay 8055 - #314

Merged
jonoirwinrsa merged 3 commits into
masterfrom
docs/deepgram-engine-port
Aug 11, 2026
Merged

docs(deepgram): note that the Engine port must stay 8055#314
jonoirwinrsa merged 3 commits into
masterfrom
docs/deepgram-engine-port

Conversation

@jonoirwinrsa

@jonoirwinrsa jonoirwinrsa commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Self-hosted Deepgram apps take ~40s to load models on a cold start. Requests that arrive in that window are queued and served once the Engine is ready — but only if the Engine's [server] port is left at the documented 8055, which Cerebrium uses to tell when it can serve. Change it and those requests fail with 503 Please try again later instead.

  • Warning before the engine.toml block: keep the port at 8055, and keep api.toml's driver_pool URL pointing at it.
  • Same note inline in both snippets, since those get copied and edited.

No behaviour change — documents an existing requirement.

Cerebrium detects that a Deepgram app is ready to serve traffic by watching the
Engine's server port, so changing it in engine.toml makes requests arrive before
the Engine can answer them and fail with 503 while the app starts up.

Add a warning before the engine.toml block and call it out inline in both the
engine.toml and api.toml snippets, since those get copied and edited.
@mintlify

mintlify Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cerebrium 🟢 Ready View Preview Aug 11, 2026, 7:46 PM

Say what keeping 8055 buys the user - startup requests are queued rather than
returning 503 - rather than describing how readiness is detected.
@jonoirwinrsa
jonoirwinrsa merged commit 74f8ab8 into master Aug 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants