If you only have one server, that isn’t production or search isn’t important.
So it doesn’t really matter how you update it.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 9, 2020, at 7:48 AM, Paras Lehana wrote:
>
> Hey Erick,
>
> Thanks for
For master/slave clusters, we have a deploy step that copies the config files
to each server. Then we restart the Solr process. We do that one at a time for
minimal service interruption.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 9, 2020, at
Hey Erick,
Thanks for your reply.
We have only one production server and one development server both
connected with same git repo (different branches). I'm using Solr in
standalone mode.
On Thu, 9 Jan 2020 at 19:48, Erick Erickson wrote:
> There’s nothing built in to Solr that will automatical
There’s nothing built in to Solr that will automatically pull files from a
VCS repo, so it’s a manual process. Which is one of the “gotchas” about
managed config files, but that’s another rant.
Are you running SolrCloud or stand-alone? If SolrCloud, it doesn’t make
sense to talk about /var/solr/da
Hi Community,
We have just set up a new server with Solr 8.4 on production. Instead of
changing files like solrconfig and solr.in.sh by logging on the server, we
are planning to have some VCS. We have integrated GIT on our server but, as
other servers, there is a single directory where git files a
