[
https://issues.apache.org/jira/browse/SOLR-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267571#comment-15267571
]
Shawn Heisey commented on SOLR-9054:
------------------------------------
bq. The location where Solr is mounted is not to be considered a
user-configurable value
+1 from me.
Echoing my comment on SOLR-9000: I'm all for configurability ... but if
*everything* is configurable, our job as developers gets a lot harder.
I once read a really interesting message on the OpenNMS user list that comes to
mind on this issue. Somebody wanted to know why the IP address of a node was
used as the primary key in the database, instead of something more useful to
them, like a hostname, and I thought the response was particularly insightful
regarding foundations and flexibility:
https://sourceforge.net/p/opennms/mailman/message/18840361/
> 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
