Implement guidellm UI #169
Conversation
|
|
||
| 1. Use the Hosted Build (Recommended for Most Users) | ||
|
|
||
| After running a benchmark with GuideLLM, a report.html file will be generated (by default at guidellm_report/report.html). This file references the latest stable version of the UI hosted at: |
There was a problem hiding this comment.
This is based off of a WIP effort i have. I don't know if this is where report.html will end up but that is what I'm working with for now.
|
📦 Build Artifacts Available |
| npx serve out | ||
| ``` | ||
|
|
||
| This will start a local server (e.g., at http://localhost:3000). Then, in your GuideLLM config or CLI flags, point to this local server as the asset base for report generation. |
There was a problem hiding this comment.
This is not something I've set up yet. Currently in this file the asset bases are configured via environment. One for prod, staging, dev, and local. But what I have in the readme implies you can see it to something other than the preconfigured options. Maybe it'd be better to have local hardcoded to localhost:3000 and wait on adding an option for the user to configure. Not sure.
|
|
||
| ### 🚧 Future Possibilities | ||
|
|
||
| We're evaluating options for hosting dev/staging/prod builds on GitHub Pages. For now, production builds will be published at: |
There was a problem hiding this comment.
I think we should go with GitHub pages. I just left the other ideas in there as food for thought since gh pages is being used for docs right now, but I think these things can coexist. Netlify seems like something common in OS repos, and this is currently a Next.js app so Vercel also seems like a reasonable choice.
This PR actually implements the application logic including the UI/charts and the api setup that retrieves data from the window object.