[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895278#comment-17895278
]
Eric Pugh commented on SOLR-7871:
---------------------------------
Hi all.. I'd like to take to another, but fresh run, at this idea. I'm
going to come from the perspective that I've formed from using Ruby on Rails,
that you have a configuraiton that establishes what your environment looks
like. To learn more about on Rails does it, check out this (GPT) summary:
[https://poe.com/s/MvWTBLoLz7S60kCKaKPE]
What does this look like for Solr?
We introduce two default files. development.yml and production.yml. They
live in ./server/solr/environments directory. When you run bin/solr start,
you automagically reading in the development.yml. You start bin/solr start -e
production and you read in production.yml. You can create your own as well.
How do we adopt this?
Start with bin/solr start and bin/solr stop command.
Ensure that bin/solr start feeds all the vairous enviornment/system properties
into a running Solr.
Then expand to the other bin/solr commands to make sure they are using this
configuration.
Then, deprecate in 9x solr.in.sh and solr.in.cmd.
Make sure the start service continues to function.
Then, in 10x remove solr.in.sh and solr.in.cmd in favour of the environment
based configuration files.
the configuraiton files will list out ALL of the various sytem properties with
some short comments, and have them enabled and disable as makes sense for that
envionment.
> Platform independent config file instead of solr.in.sh and solr.in.cmd
> ----------------------------------------------------------------------
>
> Key: SOLR-7871
> URL: https://issues.apache.org/jira/browse/SOLR-7871
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.2.1
> Reporter: Jan Høydahl
> Priority: Major
> Labels: bin/solr
> Attachments: SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch,
> SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch,
> SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch,
> SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch
>
>
> Spinoff from SOLR-7043
> The config files {{solr.in.sh}} and {{solr.in.cmd}} are currently executable
> batch files, but all they do is to set environment variables for the start
> scripts on the format {{key=value}}
> Suggest to instead have one central platform independent config file e.g.
> {{bin/solr.yml}} or {{bin/solrstart.properties}} which is parsed by
> {{SolrCLI.java}}.
--
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
