[
https://issues.apache.org/jira/browse/SOLR-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268222#comment-15268222
]
Valerio Di Cagno commented on SOLR-9054:
----------------------------------------
The reason we are trying to make the context configurable is: we would like to
group our cores by project/context.
It is already possible to start solr with a different coreset on a different
port but
to handle security policies it would be easier if we could do something like:
Project1 is restricted to Team1 and they can access it using host/solrPrj1
Project2 is restricted to Team2 and they can access it using host/solrPrj2
so if Team1 wish to upgrade their solr version while Team2 needs to hold on a
previous version for a little more time we could do it without having to change
the applications accessing solr.
Which is actually the very same reason a lot of enterprises use jndi and
wallets instead of hardcoding their DB connections.
> The new GUI is using hardcoded paths
> ------------------------------------
>
> Key: SOLR-9054
> URL: https://issues.apache.org/jira/browse/SOLR-9054
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 6.0
> Reporter: Valerio Di Cagno
>
> If Apache Solr 6.0 is started without using the default context root "/solr"
> every admin service will not work properly and is not possible to use the
> provided links to go back to the old GUI.
> In the javascript files sometimes the parameter config.solr_path is ignored
> or replaced with the value /solr returning 404 on access.
> Affected files:
> solr-webapp/webapp/js/services.js
> Suggested solution:
> Complete the integration with /js/scripts/app.js
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
