epugh commented on PR #2605: URL: https://github.com/apache/solr/pull/2605#issuecomment-2281249722
I got it to run! `http://localhost:8983/solr/compose`! So, it might be a bit of bike shedding, but I wonder if it should just be called `ui`? Just to distingush it from `admin`? Or maybe just refer to it as `compose` everywhere, instead of `compose-ui`? So, thinks I would like to see are: 1) How does this handle authentication/authorization. I'm hoping we have some really nice support that can leverage what solr already has. 2) I'm very curious to see "how easy is it to expose a simple V2 Rest api". I'm hopeful that we can leverage the great v2 openapi work to get a lovely kotlin client (instead of hand writing it like you had to for the Java properties). --> This would help me better understand how we can get more admin tool with less work! 3) if a core aspect is running it as a local client, that connects to a remote Solr (as well as a web app!), then I'd love to see more about how that app might be packaged up and distributed and connect to arbitrary Solr! 4) Lastly, if there is a lot of pushback on shipping another large webapp in solr, could this app be distributed as a Solr package? Similar to how https://github.com/o19s/splainer?tab=readme-ov-file#splainer-package-for-solr packages up a angularjs app for Solr. Very encouraging! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
