Fix Langfuse environment variables in CD workflow#29
Conversation
Pass VITE_LANGFUSE_PUBLIC_KEY and VITE_LANGFUSE_BASE_URL via build-args in `.github/workflows/cd.yaml` to ensure Langfuse features work in the production frontend environment. Co-authored-by: MrOrz <108608+MrOrz@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
🤖 Hi @MrOrz, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
🤖 I'm sorry @MrOrz, but I was unable to process your request. Please see the logs for more details. |
1 participant
This submission fixes an issue where Langfuse feedback features were not working in production deployments due to missing environment variables during the Docker build process in
cd.yaml. I addedVITE_LANGFUSE_PUBLIC_KEYandVITE_LANGFUSE_BASE_URLas build arguments, matching the configuration indeploy.yml. Tests were run to ensure no regressions.PR created automatically by Jules for task 12496008462108166446 started by @MrOrz