I see it can be a hassle to bootstrap things. Feel free to make PR to introduce such PRECREATE_ARGS option or similar. You may want to start with filing a JIRA.
Jan > 8. apr. 2025 kl. 11:23 skrev Torsten Krah <krah...@gmail.com>: > > Am Dienstag, dem 08.04.2025 um 11:09 +0200 schrieb Jan Høydahl: >> Due to limitations like this, I'd recommend moving away from solr- >> precreate and instead start an "empty" solr, and then boostrap it >> with API commands. >> >> Jan > > Might work too in some scenarios, but solr-precreate has its usecases > imho. > > With solr-precreate you can embed it in e.g. a docker-compose setup > like this: > > solr: > image: solr:9.8.1 > ... > command: > - solr-precreate > - mycore > - /mycore > > and you're done with the whole thing and can include it in various > compose stacks or the equivalent usage in k8s deployments. > > Having an empty instance startet you would now need additional > boilerplate to bootstrap the whole thing (which is possible of cause > but not as nice as it is now). > > Why not just add an env variable e.g. PRECREATE_ARGS="--user-managed" > and put it in the solr-precreate script: > > exec solr-fg "$PRECREATE_ARGS" > > That way the user could customize the starter options for precreate > too, opinions? > > Torsten >
