NikolaiJDev commented on PR #2818:
URL: https://github.com/apache/solr/pull/2818#issuecomment-2520090026

   
   > Yes, what I (and probably others as well) would like to see is how it 
would integrate into the current project (which is as described above an open 
TODO), how someone would work and test the code base (like running the UI with 
`npm ng serve`), and where the webapp can be accessed / seen (like at 
`localhost:3000`). I believe the module's / angular project's README file is 
the best place to tell other developers how to get started with this 
sub-project. Angular already provides some basic information, this could be 
extended.
   
   
![image](https://github.com/user-attachments/assets/0bd2c41a-4c05-4be8-be10-c9c917a197cc)
   It will be integrated same way as it was done before because it has to be 
shipped together with main application then using Gradle service is a great 
practice, you asked me to be waved out current application from new one, so I 
removed the concept of integration for time being. However, the refactoring of 
the Gradle job and few changes to the web.xml might be required to provide to 
fully support the current approach. As I've already mentioned to you previously 
- It might be also required to make some tweaks and changes in the Backend 
filter, what we can only understand on the stage of integration, I hope it 
won't be required, but It may.
   
   > 
   > I meant starting and poking around, yes. So there is no state yet that 
makes request to a Solr backend, is that correct?
   > 
   > I think you removed a few too manyfiles in your latest updates. The 
environment files under `/src/environments` are missing and causing an error 
when launching the app with `ng serve`.
   > 
   > And one last tip, it's fine and also recommended to include 
`package-lock.json` in the VCS, as it ensures reproducable states of the 
project. :)
   
   Well, git shows me that envs are in place, I trigger the update as well for 
that.
   As well, I want to inform to run correctly app, you need to have either 
docker container with working solr application or it must run from the same 
hostname, just for clarification localhost that you are running from isn't same 
as for backend, CORS will appear to avoid it you need to make a proxy 
configuration such as Nginx server which will locate UI and middle tier 
application under same umbrella scope. It will help browser to avoid this 
issue. Because we will emulate same patter as if it will be run from same space 
or machine as backend application.
   


-- 
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: issues-unsubscr...@solr.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to