mirror of
https://github.com/run-llama/llama_deploy.git
synced 2026-08-24 21:01:26 -04:00
[PR #525] [MERGED] Add streaming and web socket support to UI proxy #524
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/run-llama/llama_deploy/pull/525
Author: @adrianlyjak
Created: 5/31/2025
Status: ✅ Merged
Merged: 6/3/2025
Merged by: @masci
Base:
main← Head:stream📝 Commits (1)
17ef7cbAdd streaming and web socket support to UI proxy. Adjust basic UI to better support images📊 Changes
12 files changed (+4441 additions, -115 deletions)
View changed files
➕
examples/quick_start/ui/app/confetti/page.tsx(+64 -0)📝
examples/quick_start/ui/app/page.tsx(+25 -15)📝
examples/quick_start/ui/next.config.ts(+4 -2)📝
examples/quick_start/ui/package.json(+10 -7)➕
examples/quick_start/ui/pnpm-lock.yaml(+3783 -0)📝
llama_deploy/apiserver/routers/ui.py(+165 -23)📝
pyproject.toml(+4 -2)📝
templates/basic/ui/app/page.tsx(+2 -2)📝
templates/basic/ui/next.config.ts(+2 -1)📝
tests/apiserver/routers/test_deployments.py(+6 -2)📝
tests/apiserver/routers/test_ui.py(+338 -38)📝
uv.lock(+38 -23)📄 Description
This adds streaming support, both HTTP and websockets:
Also noticed basic example had issues with images not rendering, perhaps introduced by the
basePathchange. To workaround, this introduces some new environment variables. Unfortunately next.js just doesn't takebasePath(or assetPrefix I think?) into account for images, so you manually need to prepend the path from some sort of configuration.https://nextjs.org/docs/app/api-reference/config/next-config-js/basePath#images
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.