[ 
https://issues.apache.org/jira/browse/SOLR-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703180#comment-17703180
 ] 

Jan Høydahl commented on SOLR-16465:
------------------------------------

Hi.

I'd appreciate any effort to get us off of angularJs. I don't imagine I'll 
deveote much time to this in this phase. Perhaps once a foundation is laid and 
a sub-Jira created for each remaining screen to port over, I'd embrace some of 
those. This splitting up the elephant seems to have played out well on the 
JAX-RS front!

On a related note, I keep dreaming we had standalone Admin UI application which 
could be deployed in the frontend-VLAN where you could naturally allow traffic 
from humans. Then you could also de-couple stuff like Authentication, a human 
user could authenticate with OpenID-Connect, while the Admin-app could talk to 
Solr backend using BasicAuth. It's not natural to allow browser-traffic inside 
the data-VLAN where Solr is normally deployed. You'd also get rid of CORS 
issues and private/public host-name issues. In a future AdminUI reboot I'd at 
least consider the possibility of such a split, but it would of course be a 
much bigger project.

> Start the migration of the Admin UI to React
> --------------------------------------------
>
>                 Key: SOLR-16465
>                 URL: https://issues.apache.org/jira/browse/SOLR-16465
>             Project: Solr
>          Issue Type: Wish
>          Components: Admin UI
>            Reporter: Jeb Nix
>            Priority: Major
>
> I suggest using 
> [ngUpgrade|https://angular.io/guide/upgrade#upgrading-with-ngupgrade] to 
> start a linear migration process to Angular from Angular JS. ngUpgrade will 
> reach the end of life at the end of 2023, so we will only get a year of using 
> it seamlessly, but this seems to me like the last resort regarding a linear 
> migration of the Admin UI codebase. The need for this is of course to migrate 
> the current Admin UI project to newer technology, instead of writing it all 
> from the start (or implementing the same stuff once more in YASA).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to