Deploy FastAPI + Deepgram bot to JustRunMy.App

[machinatororis]

Description

Deploy the Dockerized webhook version of the bot to JustRunMy.App and ensure it runs 24/7 using Telegram webhooks.

---

Tasks

• Create a new service/application on JustRunMy.App.
• Configure the service to build from the project Dockerfile.
• Set required environment variables:
  • TELEGRAM_TOKEN
  • DG_API_KEY
  • TRANSCRIBER_BACKEND=deepgram
  • RUN_MODE=webhook (if used)
• Deploy the service and obtain the public HTTPS URL.
• Register Telegram webhook using setWebhook:
  • URL format: <public-url>/webhook
• Verify bot functionality:
  • Bot responds to messages in Telegram.
  • Service does not crash under normal usage.
• Update README:
  • Add “Cloud Deployment” section.
  • Describe architecture: Telegram → Webhook → FastAPI → Deepgram.

---

Acceptance Criteria

• Bot responds correctly to Telegram messages via webhook.
• Service remains online without manual restarts.
• README contains up-to-date deployment documentation.

[successwyh00-lgtm]

This is a very workable deployment task.

What stands out to me is that the hard part is not just getting the container to boot — it is making the webhook path stable end-to-end:

• public HTTPS URL is reachable by Telegram
• setWebhook points to the exact deployed path
• environment variables are wired correctly for webhook mode
• the app stays healthy after deployment instead of only passing a first boot check

I’ve worked on very similar bot/webhook deployment and reverse-proxy debugging work before (Docker, webhook registration, public callback routing, production fixes).

If helpful, I can contribute in one of two lightweight ways:

1. outline the minimum reliable deployment path for JustRunMy.App + Telegram webhook, or
2. help turn this into an implementation/PR checklist that reduces the usual webhook deployment pitfalls.

Either way, this looks like a good candidate for a clean “deploy first, document second” path.

[successwyh00-lgtm]

Hi, quick follow-up — this looks very doable from the deployment side.

If useful, I can help turn it into a compact rollout path covering hosting/runtime setup, webhook expectations, config pitfalls, and post-deploy verification.