Skip to content

fix: point LMS and Studio at the ai-translations container - #235

Open
jristau1984 wants to merge 1 commit into
masterfrom
jristau/ai-translations-container-url
Open

jristau1984 wants to merge 1 commit into
masterfrom
jristau/ai-translations-container-url

Conversation

@jristau1984

Copy link
Copy Markdown

AI_TRANSLATIONS_API_URL in py_configuration_files/lms.py and cms.py was http://localhost:18760/api/v1. Inside the LMS and CMS containers, localhost is the container itself, so every server-side call to ai-translations failed with a connection error.

ai-translations' own docker-compose.yml runs the app as ai-translations.app on the devstack_default network, so this switches both settings to http://ai-translations.app:18760/api/v1. Browser-side MFE plugins are unaffected; they still use localhost:18760 from the host.

Part of LP-410.

Testing (local devstack, ai-translations provisioned with its provision-ai-translations.sh), calling /available_languages/ from inside edx.devstack.lms with a JWT for the edx user:

  • http://localhost:18760/api/v1: ConnectionError
  • http://ai-translations.app:18760/api/v1: 400 {"message":"The parameter course_id is required."}, meaning the request reached the service and the JWT was accepted
  • After the change, LMS and CMS both resolve the new URL and reach the service; both heartbeats return 200.

Note: This PR was generated with Claude Code (AI-assisted) on behalf of @jristau1984.

🤖 Generated with Claude Code

AI_TRANSLATIONS_API_URL used localhost:18760, which inside the LMS and
CMS containers is the container itself, so every call to the service
failed with a connection error. ai-translations' docker-compose runs
the app as ai-translations.app on the devstack_default network, so
use that hostname instead.

Part of LP-410.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vgulati-apphelix
vgulati-apphelix force-pushed the jristau/ai-translations-container-url branch from faf45dd to a3bf2ea Compare November 4, 2026 21:25
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.

1 participant