-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 5.2.1
-
Fix Version/s: 6.3
-
Component/s: scripts and tools
-
Labels:None
I've seen a fair number of users customizing solr.in.* scripts to make changes to their Solr installs. I think the documentation suggests this, though I haven't confirmed.
One possible problem with this is that we might make changes in those scripts which such a user would want in their setup, but if they replace the script with the one in the new version, they will lose their customizations.
I propose instead that we have the startup script look for and utilize a user customization script, in a similar manner to linux init scripts that look for /etc/default/packagename, but are able to function without it. I'm not entirely sure where the script should live or what it should be called. One idea is server/etc/userconfig.{sh,cmd} ... but I haven't put a lot of thought into it yet.
If the internal behavior of our scripts is largely replaced by a small java app as detailed in SOLR-7043, then the same thing should apply there – have a config file for a user to specify settings, but work perfectly if that config file is absent.
- is related to
-
SOLR-7871 Platform independent config file instead of solr.in.sh and solr.in.cmd
-
- Open
-